[Bro] Side effects on record fields when triggering events

Christian Kreibich christian at whoop.org
Wed Aug 31 05:44:21 PDT 2005

Okay Chema and I tracked it down to the reference counting that is going
on in the core -- upon triggering, the reference count is bumped up by 1
per matching event handler and the value eventually dies after those
handlers have been execuded. Until then any changes to the value are
visible wherever a reference to the value still exists.

I'm amazed this hasn't caused me problems earlier.


More information about the Bro mailing list