INN 2.2.2 blew up in NGfind (ng.c:278)

Bert Hyman bert at rsvl.unisys.com
Fri Apr 28 14:30:49 UTC 2000


My INND 2.2.2, running on FreeBSD 3.4 on a P-200, blew up yesterday
afternoon after running for over a month without a stop (the system
has been in service for about 3 months). 

GDB says:

>Program terminated with signal 11, Segmentation fault.
> ...
>#0  0x805f7ba in NGfind (Name=0x81ad000 "alt.conspiracy.spy") at ng.c:278 
>278             if (c == ngp[0]->Name[0] && EQ(Name,ngp[0]->Name))
>(gdb) bt
>#0  0x805f7ba in NGfind (Name=0x81ad000 "alt.conspiracy.spy") at ng.c:278 
>#1  0x8051adf in ARTpost (cp=0x8096208) at art.c:2384
>#2  0x805b68e in NCpostit (cp=0x8096208) at nc.c:197
>#3  0x805ca4d in NCproc (cp=0x8096208) at nc.c:937
>#4  0x805d14e in NCreader (cp=0x8096208) at nc.c:1164
>#5  0x8058015 in CHANreadloop () at chan.c:946
>#6  0x805b14a in main (ac=8, av=0xbfbfdd48) at innd.c:944

It appears that ngp[0] is zero at the point of failure.

Looking back in DejaNews, it looks like this identical failure has
been reported sporadically for several years, back as far as INN
1.5.1! 



--
The opinions expressed in this message are my own and are not the opinions of
anyone who does not hold those opinions.
Bert Hyman | Unisys - Roseville MN
bert at rsvl.unisys.com | (651) 635-7791 | net2: 524-7791




More information about the inn-bugs mailing list