Comment # 10
on bug 8266
from Evan Huus
Do the packets still throw the exception when your post-dissector is completely
disabled/removed? Are they really valid packets? If so, then this is a bug in
Wireshark's RTP dissector.
Posting a sample capture with some of the packets in question would be
extremely helpful.
The fact that the mid-tree exception is changing some things for the
post-dissector is potentially a separate bug. From the looks of it, the
exception is occuring after UDP finishes, so anything it adds to the tree
should be accessible.
Again, a small sample capture (just a few packets, enough to reproduce) would
make it much easier to debug.
Thanks,
Evan
You are receiving this mail because:
- You are watching all bug changes.