Segmentation faults with clients (beta.11)

[Harry Bock]

Hi Carter,

I stumbled across a segmentation fault while testing Periscope at a new
site, and I've verified that they occur with the vanilla Argus clients as
well.

The two offending Argus logs, generated with rabins/rasplit, are uploaded to
http://spanning-tree.org/~hbock/argus/

GDB backtrace for the first (hourly.20090812-08):

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7eba6b0 (LWP 22105)]
0x08082613 in ArgusCheckTime (parser=0xb7e77008, ns=0xb7e15538) at
./argus_util.c:18126
18126             start.tv_sec  = rec->argus_mar.startime.tv_sec;
(gdb) bt
#0  0x08082613 in ArgusCheckTime (parser=0xb7e77008, ns=0xb7e15538) at
./argus_util.c:18126
#1  0x08059da9 in ArgusHandleDatum (parser=0xb7e77008, input=0xb7e15008,
ptr=0xb7d21140, filter=0xb7e9767c) at ./argus_util.c:2050
#2  0x0809adb9 in ArgusReadStreamSocket (parser=0xb7e77008,
input=0xb7e15008) at ./argus_client.c:1710
#3  0x0809af99 in ArgusReadFileStream (parser=0xb7e77008, input=0xb7e15008)
at ./argus_client.c:1761
#4  0x0804cae6 in main (argc=3, argv=0xbfe833b4) at ./argus_main.c:231

By playing with GDB a bit, I can see that from this line
(argus_util.c:18114):
struct ArgusRecord *rec = (void *)ns->dsrs[0];
rec is an invalid memory location - you can't access any members of the
structure without causing a memory access violation.

Could it be possible that these logs are corrupte, or is there a bug in
ArgusCheckTime?

Harry

-- 
Harry Bock
Software Developer, Package Maintainer
OSHEAN, Inc.
Email: harry at oshean.org
PGP Key ID: 546CC353
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20090812/8455db71/attachment.html>