Re: texmacs package => how to debug an app problem under the hurd?
- To: firstname.lastname@example.org
- Subject: Re: texmacs package => how to debug an app problem under the hurd?
- From: PUYDT Julien <email@example.com>
- Date: 30 Jul 2002 17:12:53 +0200
- Message-id: <1028041973.4119.18.camel@turing>
- In-reply-to: <1028027207.2496.32.camel@maybelline>
- References: <1027351102.751.14.camel@turing> <1028024147.4110.3.camel@turing> <1028027207.2496.32.camel@maybelline>
Le mar 30/07/2002 à 13:06, Paul Emsley a écrit :
> There are several discussions of using gdb with the Hurd in the
> archives. Here is one:
Well, maybe I wasn't clear enough (at least the subject was misleading):
only texmacs freezes; I still have X+WM running fine. I can kill
texmacs, launch a new one and crash it the same way (well, waiting seems
enough to do the trick);
what I was seeking wasn't how to debug the hurd, which is far too
complicated for me, but directions such as where to look for
informations about what has gone wrong. For example on GNU/Linux, I know
that by looking in /proc/<pid>, there will be some informations...
Are there hurd-specific tools? Do usual tools provide something more?
Where to look for informations on process? Is there some
well-known-soon-to-be-fixed problem that may occur silently?
Using gdb sounds like a bad idea for a beginner like me; especially a
Thank you for your answer,
Snark on #hurd, #hurdfr
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com