[Bro-Dev] #505: Invalid Unref crash

[Bro Tracker]

#505: Invalid Unref crash
----------------------+------------------------
  Reporter:  gclark   |      Owner:
      Type:  Problem  |     Status:  new
  Priority:  Normal   |  Milestone:
 Component:  Bro      |    Version:  git/master
Resolution:           |   Keywords:
----------------------+------------------------

Comment (by gclark):

 Hmm; good point.  I found it odd that the new logging framework code
 doesn't crash given the same trace under the same conditions, though.
 Also, since the crash seems to be in the core, I'd be a little surprised
 if it was the threading / logging code in there that was doing it.

 I *did* just notice that the script path in that trace doesn't match the
 path to the bro executable; if the problem appears on a real interface as
 well, will re-run and generate a correct trace :)

 --Gilbert

 On 7/21/2011 12:28 AM, Bro Tracker wrote:
 >#505: Invalid Unref crash
 >----------------------+------------------------
 >   Reporter:  gclark   |      Owner:
 >       Type:  Problem  |     Status:  new
 >   Priority:  Normal   |  Milestone:
 >  Component:  Bro      |    Version:  git/master
 >Resolution:           |   Keywords:
 >----------------------+------------------------
 >
 >Comment (by seth):
 >
 >  >  This crash was triggered by replaying a trace through a local TAP
 >  device;
 >  >  Bro was listening on the TAP device and processing the replayed
 packets.
 >
 >  Those may be null encapsulated packets which may not be supported or
 >  supported correctly.
 >

-- 
Ticket URL: <http://tracker.bro-ids.org/bro/ticket/505#comment:3>
Bro Tracker <http://tracker.bro-ids.org/bro>
Bro Issue Tracker