https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7241
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
--- Comment #2 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2012-05-09 10:40:48 PDT ---
This is the problem that the col_set_fence() API was meant to solve. The SCTP
dissector, for example, uses it to prevent multiple (possibly different)
subdissectors from overwriting each others' COL_INFO stuff (not much can be
done for COL_PROTOCOL).
Is there something that this does better than setting a fence? Couldn't, in
your example, the RTMP dissector just set a fence after each PDU has been fully
dissected (all subdissectors, if any, called)?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
