On Sat, Nov 25, 2000 at 08:05:19AM -0500, Brad Garcia wrote:
> I would suggest compiling dnrd with debugging (-g) turned on, and the
> next time it happens attach gdb to it (gdb dnrd <pid>) and then get a
> backtrace on all threads (thread apply all bt)

Well, that was fast; as soon as dhclient restarted dnrd, it happened
again. Seems to me that select() keeps failing, but I don't see
anything in my logs...

Here's a typical backtrace:

#0 0x400ba5ed in close () from /lib/libc.so.6
#1 0x40020292 in close () from /lib/libpthread.so.0
#2 0x400c2fe7 in vsyslog () from /lib/libc.so.6
#3 0x400c2def in vsyslog () from /lib/libc.so.6
#4 0x804a638 in log_msg (type=3, fmt=0x8050d26 "select returned %s")
at common.c:131
#5 0x804e719 in run () at relay.c:187
#6 0x804c1b4 in main (argc=5, argv=0xbffff9e4) at main.c:319

The libc half of it keeps changing, but the three lowermost steps are
constant.


I've put dnrd to sleep, instead of killing it; let me know if you'd like
me to set breakpoints, print variables, etc.

--
Frederic Briere <fbriere@...> [hyrule.dyndns.org]
The second piece of paper was much easier to get. Hmm.
"Well, at least I'm not HUNGARIAN!" // "That is so low."