argus 3.0.0 rc.28 memory leaks

[carter at qosient.com]

Hey Gabriel,
I have incorporated some of it, so all is not lost!  I noticed tha the valgrind output you sent earlier indicated that it couldn't figure out if a chunk of memory was uninitialized (it did seem to lose track?). I've run into this as well from valgrind and couldn't find the cause.

I think the chunk is in the user data buffer.  If you configure argus to not capture user data, does valgrind quit complaining?

Carter

Carter Bullard
QoSient LLC
150 E. 57th Street Suite 12D
New York, New York 10022
+1 212 588-9133 Phone
+1 212 588-9134 Fax  

-----Original Message-----
From: "Gabriel L. Somlo" <somlo at cmu.edu>
Date: Wed, 20 Sep 2006 09:27:17 
To:Carter Bullard <carter at qosient.com>
Cc:Argus <argus-info at lists.andrew.cmu.edu>
Subject: Re: argus 3.0.0 rc.28 memory leaks

On Wed, Sep 20, 2006 at 01:28:05AM -0400, Carter Bullard wrote:
> Hmmmm,
> So, I'm not going to implement your memory alignment patch, as you
> remove the entire ARGUSMEMDEBUG support, which is not
> something I'm going to do.  And because there isn't a problem with the
> existing code, I'm probably not going to change it, unless there is a real
> reason to do it?  So, whats the problem?

That's OK, no biggie. I was going for legibility, and assumed that
we'd want to use something like Valgrind for debugging memory problems
anyway.

Retards,,
Gabriel