[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [GNUnet-developers] Reproduceable failure

From: Christian Grothoff
Subject: Re: [GNUnet-developers] Reproduceable failure
Date: Tue, 1 Apr 2003 08:04:53 -0500
User-agent: KMail/1.4.3

Hash: SHA1

On Monday 31 March 2003 10:56 pm, Jan Marco Alkema wrote:
> Someone told me to use the source code of the 'top' shell command for mem
> monitoring of the gnunetd process.
> >Mar 31 04:52:42 __BREAK__
> I think it is better to patch gdb in such a way that automatically after a
> segmentation error occurs a dump is made and the restart of gnunetd will be
> done. After restarting of gnunetd the "info threads dump" can be send to
> the maintainer (for example by the chat client of gnunet).
> Suggestion: If in gnunetd a __BREAK__ exception has occurred, gnunetd must
> "signal" to the patched gdb process to do an "info threads dump" at the
> place of where the __BREAK__ is made in the source code of gnunet,

Well, the thing is called "BREAK" because the idea is that if you run from 
gdb, you'll probably want to set a breakpoint there. Just do this:

(gdb) run -d -L DEBUG
(gdb) break breakpoint
(gdb) cont

and gdb will stop the execution of gnunetd whenever the breakpoint is hit, 
just as in the case of a segfault. The difference compared to a segfault is, 
that you can get a stack trace and inspect variables and continue execution 
with "cont" afterwards.

Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see


reply via email to

[Prev in Thread] Current Thread [Next in Thread]