INN 2.5.4 strange crash

[Petr Novopashenniy]

Good day, All!

On Wed, 29 Oct 2014, Julien ?LIE wrote:

[..]

J?? Is your INN built with optimizations?  It sometimes prevents gdb from giving
J?? useful information; in that case, you should try to rebuild INN with for
J?? instance
J?? "-g -O0 -fno-inline".
J?? 
J?? 
J?? In your message, the backtrace also hints at line 1284 of chan.c:
J??     (*cp->Waker)(cp);
J?? but I do not see why an error would happen here.
J?? *cp->Waker is either SITEspoolwake or CHANwakeup but I do not see
J?? what could be NULL there.
J?? 

After I rebuild INN with new flags ("-g -O0 -fno-inline"), I recently saw 
2 segfaults:

Core was generated by `innd'.
Program terminated with signal 11, Segmentation fault.
Reading symbols from /usr/local/news/lib/libinnhist.so.2...done.
Reading symbols from /usr/local/news/lib/libstorage.so.2...done.
Reading symbols from /usr/local/news/lib/libinn.so.2...done.
Reading symbols from /usr/local/lib/libdb-4.7.so...done.
Reading symbols from /usr/lib/libz.so.2...done.
Reading symbols from 
/usr/local/lib/perl5/5.8.5/mach/CORE/libperl.so...done.
Reading symbols from /usr/lib/libm.so.2...done.
Reading symbols from /usr/lib/libcrypt.so.2...done.
Reading symbols from /usr/lib/libutil.so.3...done.
Reading symbols from /usr/lib/libc.so.4...done.
Reading symbols from /usr/libexec/ld-elf.so.1...done.
#0  0x0 in ?? ()
(gdb) bt
#0  0x0 in ?? ()
#1  0x805b7f0 in CHANreadloop () at chan.c:1284
#2  0x805db7b in main (ac=0, av=0xbfbfeec4) at innd.c:750
(gdb) 


Line 1284 is still present in new gdb backtrace...

--pety