Random crashing with rc.40 on Linux

[Jonathan Towne]

On Thu, Mar 08, 2007 at 02:08:14PM +0000, carter at qosient.com scribbled:
[snip]
# 
#    argus -r dump.file -w out.file
# 

Carter,


I'm having similar crashing issues on FreeBSD 6.1-STABLE on a sensor that
has previously been very stable with rc39 and prior.

When I run argus against the captured file, it segfaults in the same way
that it does during normal operation:


(gdb) run -r argus_19:10:00 -w /dev/null
Starting program: /usr/local/sbin/argus -r argus_19:10:00 -w /dev/null
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols
found)...argus[23202]: 08 Mar 07 09:52:43.486331 started

Program received signal SIGSEGV, Segmentation fault.
0x0805223f in ArgusOpenInterface ()
(gdb) bt full
#0  0x0805223f in ArgusOpenInterface ()
No symbol table info available.
#1  0x08054d9e in ArgusGetPackets ()
No symbol table info available.
#2  0x0804bedc in main ()
No symbol table info available.



When I put the breakpoint in ArgusLog:

(gdb) b ArgusLog
Breakpoint 1 at 0x805d13e
(gdb) run -r argus_19:10:00 -w /dev/null
Starting program: /usr/local/sbin/argus -r argus_19:10:00 -w /dev/null
(no debugging symbols found)...(no debugging symbols found)...(no debugging
symbols found)...(no debugging symbols found)...(no debugging symbols found)...
Breakpoint 1, 0x0805d13e in ArgusLog ()
(gdb) bt full
#0  0x0805d13e in ArgusLog ()
No symbol table info available.
#1  0x0804c414 in main ()
No symbol table info available.




This is built with '.debug' touched in the top-level directory; is there
anything else that'll help narrow this down?  It's happening way too often
to be a fluke, and without debugging symbols I'm not sure what's up.


This sensor is continuously catching full content dumps from the network
as well, so I've got the original pcap files to work with if it will help.



-- Jonathan Towne