Re: Connection timed out

[Dan Nelson]

In the last episode (Jun 09), Herbert Straub said:
> Quoting Dan Nelson <address@hidden>:
> > instead of the 5min timeout.  If you can get a coredump and a stack
> > trace of the faulting thread, that would help.
> 
> OK, today i have got a core dump:
> 
> gdb /usr/sbin/spamass-milter
> (gdb) core core.23429-2004-06-09
> Core was generated by `/usr/sbin/spamass-milter -p
> /var/run/sendmail/spamass.sock -r y -i xx.xx.xx.xx'.
> Program terminated with signal 11, Segmentation fault.
> #0  0x0804e442 in geteuid ()
> (gdb) bt
> #0  0x0804e442 in geteuid ()
> #1  0x08067e90 in ?? ()
> #2  0x0805c6b7 in basic_string<char, string_char_traits<char>, 
> __default_alloc_template<true, 0> >::~basic_string ()
> #3  0x0805bf62 in basic_string<char, string_char_traits<char>, 
> __default_alloc_template<true, 0> >::~basic_string ()
> #4  0x0805ad69 in basic_string<char, string_char_traits<char>, 
> __default_alloc_template<true, 0> >::~basic_string ()
> #5  0x0805a57d in basic_string<char, string_char_traits<char>, 
> __default_alloc_template<true, 0> >::~basic_string ()
> #6  0x400880ba in pthread_start_thread () from /lib/libpthread.so.0
> (gdb)
> 
> Next, i compile spamass-milter with -g. Then we see more details.

Unfortunately, that trace doesn't make much sense; it looks like
basic_string's destructor called itself three times, then called
geteuid(), and _that_ seg faulted, which is impossible :) See what
"info thread" and "thread apply all bt" print; maybe one of the other
stacks make more sense.

-- 
        Dan Nelson
        address@hidden