ragator segfaults

[Peter Van Epp]

	Given it was calloc my first guess would be you ran out of memory for
some reason (too low rlimit on your task?) and it was ungraceful about it.
I'd think .debug would be easier than adding -g in the necessary places and
I'm lazy to a fault :-).

Peter Van Epp / Operations and Technical Support 

On Thu, Feb 03, 2005 at 03:22:05PM +1300, Russell Fulton wrote:
> Well I've taken a couple of steps forward now.  My OBSD configure
> problems were fixed by the .fixed.1 tgz. 
> 
> I am now playing around with the archive script and ragator dies on
> quite a small file:
> 
> -bash-3.00$ gdb bin/ragator data/ragator.core
> GNU gdb 6.1
> Copyright 2004 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you
> are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB.  Type "show warranty" for
> details.
> This GDB was configured as "i386-unknown-openbsd3.6"...
> Core was generated by `ragator'.
> Program terminated with signal 11, Segmentation fault.
> Reading symbols from /usr/lib/libm.so.2.0...done.
> Loaded symbols for /usr/lib/libm.so.2.0
> Reading symbols from /usr/lib/libc.so.34.1...done.
> Loaded symbols for /usr/lib/libc.so.34.1
> Reading symbols from /usr/libexec/ld.so...done.
> Loaded symbols for /usr/libexec/ld.so
> #0  0x1c0175e3 in ArgusCalloc ()
> (gdb) where
> #0  0x1c0175e3 in ArgusCalloc ()
> #1  0x1c01a687 in RaNewArgusStore ()
> #2  0x1c0021f9 in RaProcessSrvRecord ()
> #3  0x1c0024cf in RaProcessTCPRecord ()
> #4  0x1c001a19 in RaProcessRecord ()
> #5  0x1c0045b9 in ArgusHandleDatum ()
> #6  0x1c006d29 in ArgusReadStreamSocket ()
> #7  0x1c007531 in ArgusReadStream ()
> #8  0x1c004264 in main ()
> (gdb)
> 
> Any ideas?  Should I recompile with .debug or just add -g to CFLAGS ?
> 
> Russell