[Bro-Dev] #1004: Uninitialized memory error in optimized mode
Bro Tracker
bro at tracker.bro.org
Wed May 15 17:42:27 PDT 2013
#1004: Uninitialized memory error in optimized mode
---------------------+------------------------
Reporter: robin | Owner:
Type: Problem | Status: new
Priority: High | Milestone: Bro2.2
Component: Bro | Version: git/master
Keywords: |
---------------------+------------------------
Bernhard and I have started to see this on two independent Fedora 18
machines running 4.7.2:
With --enable-debug, everything runs fine. Without (and hence optimization
turned on), a number of btests fail. Tracking down one, the attached trace
yields the following output with {{{bro -C -r 2cx26uAvUPl
testing/btest/core/conn-uid.bro}}}
{{{
[orig_h=4087:d701::fbf5:5d00:0:0, orig_p=0/tcp,
resp_h=a078:de02::92ce:5e00:0:0, resp_p=0/tcp], rkiDR8g5bV7
[orig_h=4087:d701::fbf5:5d00:0:0, orig_p=0/tcp,
resp_h=a078:de02::92ce:5e00:0:0, resp_p=0/tcp], rkiDR8g5bV7
}}}
Correct is:
{{{
[orig_h=141.142.220.235, orig_p=6705/tcp, resp_h=173.192.163.128,
resp_p=80/tcp], 4JRWvfGWLMa
[orig_h=141.142.220.235, orig_p=6705/tcp, resp_h=173.192.163.128,
resp_p=80/tcp], 4JRWvfGWLMa
}}}
Valgrind reports a number of uninitialized memory error that seem related.
I'm actually seeing this with 2.1 as well, so it doesn't seem to be
anything recent; probably a compiler change that now triggers it.
--
Ticket URL: <http://tracker.bro.org/bro/ticket/1004>
Bro Tracker <http://tracker.bro.org/bro>
Bro Issue Tracker
More information about the bro-dev
mailing list