argus malloc memory corruption error

[Carter Bullard]

Oh yes, the output is the key to using valgrind.
It identifies memory issues, like writing into a block
that hasn't been allocated, and reading outside of an
initialized bit of memory.  Somewhere in there is a
line that indicates that we're reading from a block
that has been deallocated, or writing beyond a block's
size.

I'll take what you've got, and I'll compare it with
what I get, and we'll see if there is a gotcha there.

Carter 



On Aug 1, 2013, at 1:38 PM, Mike Iglesias <iglesias at uci.edu> wrote:

> On 08/01/2013 10:13 AM, Carter Bullard wrote:
>> Do you have valgrind ?
>> 
>>   # valgrind --leak-check=yes argus
> 
> I let it run for over 10 minutes and the memory corruption error did not show
> up.  It generated a lot of output though, so if you want that let me know.
> 
> 
> -- 
> Mike Iglesias
> UCI Network Security Team              Email:       security at uci.edu
> University of California, Irvine       phone:       949-824-6926
> Office of Information Technology       FAX:         949-824-2270
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6837 bytes
Desc: not available
URL: <https://pairlist1.pair.net/pipermail/argus/attachments/20130801/041bc34f/attachment.bin>