[ARGUS] Another Core Dump

[Carter Bullard]

Well, it appears that the asock pointer is getting trashed.
This value is held in an array that is stored in the ArgusOutputTask
client list.  Checking out what else may be corrupted could tell
us possibly where the problem lies.

Can you dump the ArgusOutputTask struct?

(gdb) print *ArgusOutputTask

Carter


-----Original Message-----
From: eric [mailto:eric-list-argus at catastrophe.net]
Sent: Wednesday, April 14, 2004 10:46 AM
To: Carter Bullard
Cc: 'Peter Van Epp'; argus-info at lists.andrew.cmu.edu
Subject: Re: [ARGUS] Another Core Dump

On Wed, 2004-04-14 at 10:42:41 -0400, Carter Bullard proclaimed...

> Hey Eric,
>    Hmmmm, segmentation fault, so the assumption is that the
> asock pointer is corrupt?  If you're still in the gdb, do this:
>
> (gdb) print *asock
>
> to see what is going on.  It maybe that the segmentation fault
> is occurring at the line before.  If we can figure out which
> area of memory is foobar, then we can fix it pronto.

Hi Carter,

Here's the results.

(gdb) print *asock
Cannot access memory at address 0x8181000.

I have yet to see argus crash when running out of gdb (it's been
doing so for about 7 hours now) and when it dies off, I'll send the
details.

- Eric