Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-bugs: [Wireshark-bugs] [Bug 7638] Buildbot crash output: randpkt-2012-08-15-7567.pcap

Date: Wed, 15 Aug 2012 13:48:57 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7638

--- Comment #4 from Michael Mann <mmann78@xxxxxxxxxxxx> 2012-08-15 13:48:57 PDT ---
The GIOP protocol supports both big and little endian values depending on the
version (in the header of the message), which can affect the "message size". 
Should there be a "sanity check" based on the version of the message and just
set some expert info?  Should the "sanity check" cause the heuristic to fail? 
Should the dissector attempt to use the oppose endianness to see if the number
is "more valid"?

And what should the "magic number" be for that "size sanity check"?

-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.