https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7916
--- Comment #14 from Bill Meier <wmeier@xxxxxxxxxxx> 2012-10-29 12:49:23 PDT ---
>
> Yes: I was expecting that the invalid memory reference in the dissector would
> be trapped via an exception and would not cause Wireshark/tshark to actually
> crash.
>
> Without the fix in packet-mip6, I get an actual crash on my 32bit Windows
> system.
>
> I'll dig into this a bit further.
Well...
My expectation might be reasonable, but, in actuality, there's a known problem
with the Windows Wireshark handling of certain kinds of exceptions.
See: https://www.wireshark.org/lists/wireshark-dev/200704/msg00243.html
(Based upon my comment in another bug, it seems that I even knew this once upon
a time).
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
