This is getting weirder by the minute. I just restored the same
configuration I was using, so that bbproxy is back in the mix, and it's not
crashing anymore. I haven't really done anything to the machine beyond
restoring the same config I was using yesterday. Evidently whatever was
causing the problem has gone away, for now at least.
Thanks,
Larry Barber
On 5/15/07, Larry Barber <user-6ef9c2864140@xymon.invalid> wrote:
Afraid it won't be much help:
(gdb) fr 5
#5 0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
877 FD_SET(cwalk->ssocket, &fdread);
(gdb) p cwalk
No symbol "cwalk" in current context.
(gdb) p cwalk->ssocket
No symbol "cwalk" in current context.
(gdb) p fdread
No symbol "fdread" in current context.
Thanks,
Larry Barber
On 5/15/07, Henrik Stoerner <user-ce4a2c883f75@xymon.invalid> wrote:
On Tue, May 15, 2007 at 08:49:30AM -0500, Larry Barber wrote:
Yesterday, for no apparent reason, bbproxy started crashing every few
minutes. Has anybody else had this problem? Here is the stack trace:
(gdb) where
#3 0x0804e5e2 in sigsegv_handler (signum=11) at sig.c:57
#4 <signal handler called>
#5 0x0804a8c8 in main (argc=6, argv=0xbff446f4) at bbproxy.c:877
Weird. Could you go back into gdb and do run the commands
fr 5
p cwalk
p cwalk->ssocket
p fdread
Regards,
Henrik