Sol 2.9, inn-2.4.1, innd segfaulting when article received

Ted Coady tedslists at
Tue Oct 19 20:31:45 UTC 2004

Hi all...  

Have a weird one here...  inn-2.4.1 built on a Solaris 9 box,
gcc-3.4.1 as packaged by Blastwave.  Have recently set up a feed from
one of my other boxes (with identical config, incidentally) to this
one, and now innd seems to puke as soon as it sees an incoming

gdb backtrace as follows:

Core was generated by `/opt/news/bin/innd -p 4'.
Program terminated with signal 11, Segmentation fault.
#0  0xfeec6dcc in _malloc_unlocked () from /lib/
(gdb) bt
#0  0xfeec6dcc in _malloc_unlocked () from /lib/
#1  0xfeec6b7c in malloc () from /lib/
#2  0x000697e8 in x_malloc (size=2049, file=0x109498 "art.c",
line=1404) at xmalloc.c:74
#3  0x000278e8 in ARTpost (cp=0x1c6ef8) at art.c:1404
#4  0x00031cbc in NCproc (cp=0x1c6ef8) at nc.c:196
#5  0x0002d4dc in CHANreadloop () at chan.c:1062
#6  0x0002fa1c in main (ac=1, av=0x403d) at innd.c:671

Anyone seen this before?  More importantly, anyone fixed this before?  :)

Thanks in advance...


More information about the inn-workers mailing list