Re: texmacs package => how to debug an app problem under the hurd?
- To: PUYDT Julien <email@example.com>
- Cc: firstname.lastname@example.org
- Subject: Re: texmacs package => how to debug an app problem under the hurd?
- From: Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de>
- Date: Tue, 30 Jul 2002 17:29:39 +0200
- Message-id: <20020730152938.GD631@18.104.22.168>
- In-reply-to: <1028041973.4119.18.camel@turing>
- References: <1027351102.751.14.camel@turing> <1028024147.4110.3.camel@turing> <1028027207.2496.32.camel@maybelline> <1028041973.4119.18.camel@turing>
On Tue, Jul 30, 2002 at 05:12:53PM +0200, PUYDT Julien wrote:
> 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...
If a program hangs, it hangs because it is in a loop or it is blocking on an
RPC or other event. Both can be easily seen with gdb.
> Are there hurd-specific tools?
You can try rpctrace, although it is a bit buggy itself.
> Using gdb sounds like a bad idea for a beginner like me; especially a
> guile-based app!
Using gdb is an excellent idea. You better become familiar with it today
than tomorrow. Run, not walk, to your computer and read "info gdb" :)
(install libc0.3-dbg and run programs with LD_LIBRARY_PATH=/lib/debug, so
you get debugging symbols into libc).
`Rhubarb is no Egyptian god.' GNU http://www.gnu.org email@example.com
Marcus Brinkmann The Hurd http://www.gnu.org/software/hurd/
To UNSUBSCRIBE, email to firstname.lastname@example.org
with a subject of "unsubscribe". Trouble? Contact email@example.com