SO this doesn't (at the moment) seem to be related to table expiration. My
table is maintained on manager and expire_func only runs on manager.
But, I see 'a' worker stall with 99-100% CPU for a good while while all other
workers go down to 5-6% CPU. conn.log continues to grow though
GDB
I'm doing:
gdb --interpreter mi --args "/home/default/bro/build/src/bro" -r
/tmp/arp_l2tpv3.cap
I'm using VisualGDB (http://visualgdb.com/?features=linux) to debug it from
Visual Studio as I've done with tons of other projects. It just execute the
gdb commands over SSH So its basically the same
> On Jan 19, 2017, at 5:32 PM, Alberto Garcia wrote:
>
> I've tried running:
>
> set exec-wrapper bash -c 'source /home/default/bro/build/bro-path-dev.sh'
> within GDB but it didn't work either.
>
> On Thu, Jan 19, 2017 at 4:01 PM, Alberto Garcia
I've tried running:
set exec-wrapper bash -c 'source /home/default/bro/build/bro-path-dev.sh'
within GDB but it didn't work either.
On Thu, Jan 19, 2017 at 4:01 PM, Alberto Garcia
wrote:
> It actually works if i'm in a shell but not if I'm debugging it with dbg.
> It
It actually works if i'm in a shell but not if I'm debugging it with dbg.
It still shows the same error when executing main.cc:759 -->
add_input_file("base/init-bare.bro");
Is there anything I need to execute from within dbg to set the environment
variables while using gdb?
Thank you again
On
Easy one!
thanks!
On Thu, Jan 19, 2017 at 2:46 PM, Johanna Amann wrote:
> On Thu, Jan 19, 2017 at 11:19:20AM -0600, Alberto Garcia wrote:
> > Hi,
> >
> > I've compiled bro from source to do some debugging. Once compiled I can't
> > run bro since there is an error popping up:
On Thu, Jan 19, 2017 at 09:44 -0800, you wrote:
> Still, to clearify, there might be a possibility that because at
> present table_incremental_step=5000, somehow expiring >> 5000 entries
> continiously every moment might cause cause Queue to deadlock
> resulting in BRO to stop packets
> On Jan 18, 2017, at 10:28 AM, Robin Sommer wrote:
>
> I also think it would be quite useful to test packages before
> installing them
Maybe I’m not so much questioning whether to run tests before or after
installation, but rather if the testing sandbox should include
Hi,
I've compiled bro from source to do some debugging. Once compiled I can't
run bro since there is an error popping up:
default@debian:~/bro$ ./build/src/bro
fatal error: can't find base/init-bare.bro
If I do the make install and then call bro from /usr/local/bro/bin/bro it
works fine.
What
> But I also wonder what you are doing that is triggering
> Dictionary9NextEntryERP7HashKeyRP10IterCookiei
>
> which would be
>
> void* Dictionary::NextEntry(HashKey*& h, IterCookie*& cookie, int
> return_hash) const
>
> Tables should be fine, but I wonder what you're doing that is triggering
10 matches
Mail list logo