Segfault when running possibly silly command line options

[Carter Bullard]

Hey Jesse,
Excellent, a bug report ;O)  It's having problems with the first management record trying to print one of the obscure time attributes.  How does it do without the man records ?  Can you run it with the filter " - not man " ?

I try to fix this tonight when I can get to the code.

Carter

On Sep 26, 2012, at 11:29 AM, Jesse Bowling <jessebowling at gmail.com> wrote:

> In trying to explore what data the various dsrs contain, I ran across a segfault. It's possible that no one would actually want to run with the options I'm using, but I'll report this just to make the issue known...
> 
> Starting program: /usr/local/bin/ra -F /usr/local/src/argus-clients-3.0.6.2/support/Config/rarc.print.all.conf  -r argus.2012.09.13.15.15.00.gz -M dsrs=flow -L -1 -N 1
> [Thread debugging using libthread_db enabled]
> 10.10.10.10,,0,0,06:43:33.213730,06:43:31.623988,0.000000,,06:43:31.623988,06:43:33.213730,0.000000,0.000000,06:43:31.623988,06:43:33.213730,1347533013.21373,0,,,,          ,,,,,,0,0,,0,0,man,0,0,,,,,,,,,,,,,0,0,0,0,0,0,0,0,0,0.000000,0.000000,0.000000,0.000000,0.000000,0.000000,0,0,0,0.000000,0.000000,0.000000,0,0,0,0.000000,0.000000,0.000000,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,STA,Start,,,,,,,,,,,,,,,,0.000000,,,,0.000000,,,,,,,,,,,,,,,0.000000,0.000000,,,,,,,,,0.000000,0.000000,0.000000,,,,,
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x0000000000419530 in ArgusPrintRelativeDate (parser=0x7ffff7e9f010, buf=0x7ffffff9d7e0 "", argus=0x7ffff7e3d620, len=12) at ./argus_util.c:4202
> 4202             parser->ArgusStartTimeVal.tv_sec  = dtime->src.start.tv_sec;
> (gdb) print parser->ArgusStartTimeVal.tv_sec
> $1 = 0
> (gdb) print dtime->src.start.tv_sec
> Cannot access memory at address 0x4
> 
> Cheers,
> 
> Jesse
> 
> -- 
> Jesse Bowling
> 
>