Michael Mann
changed
bug 9332
Comment # 2
on bug 9332
from Michael Mann
Not sure what the "right" fix for this is. Can also duplicate on SVN, but I'm
not sure the DISSECTOR_ASSERT is in the same place as 1.10 (haven't checked)
Yes there could be a payload > 0 check in the websocket dissector, but the
DISSECTOR_ASSERT comes from inside proto_tree_add_item (tvb_memcpy call inside
tvb_get_string). This appears to be the result of recent "string behavior"
work, r52651 introduced the DISSECTOR_ASSERT.
You are receiving this mail because:
- You are watching all bug changes.