[Bro] Memory leak output

[Josh Liburdi]

Wow, thanks Jon-- that helped a lot. When you test with perftools, do
you do anything different aside from change the configure options
(--enable-debug --enable-perftools-debug) and run without valgrind?

On Tue, Feb 3, 2015 at 8:12 AM, Siwek, Jon <jsiwek at illinois.edu> wrote:
>
>> On Feb 2, 2015, at 7:01 PM, Josh Liburdi <liburdi.joshua at gmail.com> wrote:
>>
>> Thanks Jon. I have a simple program that definitely leaks memory and
>> valgrind reports this accurately, but I still cannot get it to work
>> with Bro. If you have time, would you copy / paste the command line
>> arguments you use to test Bro with valgrind?
>
> git clone --recursive git://git.bro.org/bro bro-tmp
> cd bro-tmp
> ./configure --enable-debug --disable-perftools
> cd build/
> make -j8
> . bro-path-dev.sh
> valgrind --leak-check=yes ./src/bro -r ../testing/btest/Traces/http/get.trace
> ==12109== Memcheck, a memory error detector
> ==12109== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
> ==12109== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
> ==12109== Command: ./src/bro -r ../testing/btest/Traces/http/get.trace
> ==12109==
> ==12109==
> ==12109== HEAP SUMMARY:
> ==12109==     in use at exit: 30,275,602 bytes in 434,261 blocks
> ==12109==   total heap usage: 1,340,380 allocs, 906,119 frees, 115,312,199 bytes allocated
> ==12109==
> ==12109== 1 bytes in 1 blocks are definitely lost in loss record 2 of 5,455
> ==12109==    at 0x4A06A2E: malloc (vg_replace_malloc.c:270)
> ==12109==    by 0x3FB6080E91: strdup (in /lib64/libc-2.12.so)
> ==12109==    by 0x6D3585: main (main.cc:533)
> …
>
> - Jon