[ARGUS] Another Core Dump

[Carter Bullard]

Well, there you go.  While the ArgusOutputTask.client[0] struct looks
decent, the output socket fd is -1.  This isn't right, since we shouldn't
have gotten this far if the (fd == -1).

So in your backtrace, you're calling ArgusWriteSocket with (asock ==
0x8181000)
but the client has the socket as, (ArgusOutputTask.clients[0].sock ==
0x8160000).

Could you print out this info?

(gdb) print ArgusOutputTask
(gdb) print &ArgusOutputTask.clients[0]
(gdb) print *ArgusOutputTask.clients[0].sock

Carter


-----Original Message-----
From: owner-argus-info at lists.andrew.cmu.edu
[mailto:owner-argus-info at lists.andrew.cmu.edu] On Behalf Of eric
Sent: Wednesday, April 14, 2004 10:53 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:51:40 -0400, Carter Bullard proclaimed...

> 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

Here ya go...

(gdb) print *ArgusOutputTask
$1 = {pid = 0, clienttags = 1, client = {{fd = -1, pid = 53991, pipe = {8,
9},
      sock = 0x8160000}, {fd = -1, pid = -1, pipe = {-1, -1}, sock = 0x0}, {
      fd = -1, pid = -1, pipe = {-1, -1}, sock = 0x0}, {fd = -1, pid = -1,
      pipe = {-1, -1}, sock = 0x0}, {fd = -1, pid = -1, pipe = {-1, -1},
      sock = 0x0}}}