[Bro] Memory leak output

Josh Liburdi liburdi.joshua at gmail.com
Mon Feb 2 19:07:47 PST 2015

Same for me, but at the least it should be reporting leaks in the init routines. Since I'm working on an analyzer I'm pretty determined to get this working accurately ... 


On Monday, Feb 2, 2015 at 5:27 PM, John Donnelly <jdonnelly at dyn.com>, wrote:

valgrind --log-file=val.txt --tool=memcheck --leak-check=full -v /opt/bro/bin/bro -i lo -i eth0 -i eth1 -b -C /opt/bro/share/bro/base/protocols/dns/main.bro 

The results are saved in "val.txt" 

I haven't seen any reports of leaks . 

On Mon, 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?

On Mon, Feb 2, 2015 at 2:52 PM, Siwek, Jon <jsiwek at illinois.edu> wrote:


>> On Feb 2, 2015, at 3:26 PM, Josh Liburdi <liburdi.joshua at gmail.com> wrote:


>> Addtionally, my Bro debug.log is empty.


> An empty debug.log is fine.  It only has contents if at least one of the various debug streams is enabled via a -B<stream> flag when running bro.  DebugLogger::streams in src/DebugLogger.cc has a list of stream names.


>> On Mon, Feb 2, 2015 at 1:25 PM, Josh Liburdi <liburdi.joshua at gmail.com> wrote:

>>> That's odd, I am using the configuration referenced on the Finding

>>> Memory Leaks page: ./configure --enable-debug --enable-perftools

>>> --enable-perftools-debug


>>> I tried your configuration as well and receive the same results

>>> (gperftools reports memory leaks but can't find thread stacks,

>>> valgrind finds no memory leaks whatsoever). There must be something

>>> wrong with one of my installations.


> For valgrind, maybe check that ~/.valgrindrc, $VALGRIND_OPTS, ./.valgrindrc aren’t doing something to change leak-check behavior and make sure to do —leak-check=full.


> For either pprof or valgrind, maybe make sure the bro binary is the one you expect (i.e. use a full path) and that it’s not a script or other program that just exec’s bro.


> Otherwise, maybe you’ll have to start troubleshooting from a simple toy program that you’ve written and know always leaks memory.


> - Jon


Bro mailing list
bro at bro-ids.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/bro/attachments/20150202/caed9b1f/attachment.html 

More information about the Bro mailing list