Comment # 8
on bug 9983
from Michael Mann
(In reply to comment #7)
> Best
> I can figure is that it has something to do with proto_tree_add_bytes_format
> being the last proto_tree_add call in the frame and it's less picky about
> length. Is this another TRY_TO_FAKE_THIS_ITEM issue?
I switched the proto_tree_add_bytes_format calls with proto_tree_add_item and
exception is thrown every time and malformed packet shows up in Expert Info.
Packet is also noted as [Malformed] in the INFO column (it's not when
proto_tree_add_bytes_format is used, just in detail pane).
You are receiving this mail because:
- You are watching all bug changes.
