[Bro] crash with std::bad_alloc

rmkml rmkml at free.fr
Thu Nov 6 21:24:11 PST 2008


Hi Peter,
or another idea: load heavy-analysis.bro for reducing *_timeout.
Regards
Rmkml
Crusoe-Researches.com

On Thu, 6 Nov 2008, Christian Kreibich wrote:

> Date: Thu, 06 Nov 2008 17:49:51 -0800
> From: Christian Kreibich <christian at whoop.org>
> To: Peter Wurzinger <pw at seclab.tuwien.ac.at>
> Cc: Bro at bro-ids.org, Robin Sommer <robin at icir.org>
> Subject: Re: [Bro] crash with std::bad_alloc
> 
> On Thu, 2008-11-06 at 12:23 +0100, Peter Wurzinger wrote:
>> I reran my code using profiling.bro. The memory consumption continuously
>> increased, and the last lines before crashing were:
>>
>> Memory: total=3126520K total_adj=3116888K malloced: 2878549K
>
> Try running Bro for a limited amount of time and load print-globals.bro,
> as pointed out at:
> http://www.bro-ids.org/wiki/index.php/Development_HOWTOs#print-globals.bro
>
> Upon termination, Bro will tell you the amount of memory your global
> variables have accumulated. If you have a state-keeping problem in one
> of those variables, you'll spot the issue there.
>
> -- 
> Cheers,
> Christian
>
> _______________________________________________
> Bro mailing list
> bro at bro-ids.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/bro
>


More information about the Bro mailing list