ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 7210] Buildbot crash output: fuzz-2012-04-27-376.pcap

Date: Fri, 27 Apr 2012 19:38:18 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7210

--- Comment #4 from Guy Harris <guy@xxxxxxxxxxxx> 2012-04-27 19:38:18 PDT ---
(In reply to comment #3)
> "Exception Occurred" means the dissector did crash

No, it means that the dissector called a tvbuff routine to fetch some data and
the data wasn't actually present in the tvbuff; this either means

    1) the dissector is attempting to fetch data that is legitimately not
there, which is a dissector bug;

    2) the dissector is attempting to fetch data that is supposed to be there,
but that isn't there in the packet, which is *not* a dissector bug, it's a
malformed packet;

    3) the dissector is attempting to fetch data that is supposed to be there,
but isn't there because reassembly wasn't done, which is *not* a dissector bug,
it's a preference setting that prevents reassembly or something such as that;

    4) the dissector is attempting to fetch data that is supposed to be there,
and that was there in the packet, but got discarded by the snapshot length
being set, which is *not* a dissector bug, it's a case of "if you cared about
this you should have used a bigger snapshot length".

In most cases, it's 2, 3, or 4, which are, as noted, not dissector bugs, so
there's nothing to fix.

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