[Bro] Bro seg faults when used with gperftools monitoring.

Vlad Grigorescu vladg at illinois.edu
Thu Feb 16 08:14:10 PST 2017

That's a common config that we test with which I would expect to work.
Can you provide some details on how exactly you built and ran Bro?


fatema bannatwala <fatema.bannatwala at gmail.com> writes:

> So, I wanted to find out whether there are any memory leaks in any of the
> code/scripts,
> that I am loading with Bro, therefore I installed gperftools and compiled
> Bro 2.5 on a VM
> with 5GB of memory and centos 7.2.
> I loaded only the default scripts to start with, i.e didn't include any
> custom scripts in local.bro.
> I ran Bro as default on a pcap (~11G) and it terminated normally producing
> output log files.
> When I ran Bro with Perftools heap leak checker active on the same pcap, it
> seg faulted
> after some time.
> I was watching memory usage during the run and it didn't seem to be using
> 100% of available
> memory.
> Hence wanted to ask Is there any reason Bro would seg fault while run with
> HEAPCHECK enabled?
> My goal was to load custom scripts one by one and everytime run bro with
> heap check
> to see what can cause a memory leak. But stumbled upon this at the very
> beginning,
> so until I find out why it seg faulted on default configs, I can't really
> check the custom scripts/code
> for memory leak :( :(
> Including the coredump file.
> Thanks,
> Fatema.
> _______________________________________________
> Bro mailing list
> bro at bro-ids.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/bro
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 800 bytes
Desc: not available
Url : http://mailman.ICSI.Berkeley.EDU/pipermail/bro/attachments/20170216/06f7cf2d/attachment.bin 

More information about the Bro mailing list