https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=7916
--- Comment #12 from Jakub Zawadzki <darkjames-ws@xxxxxxxxxxxx> 2012-10-29 08:31:26 PDT ---
(In reply to comment #11)
> (In reply to comment #10)
> > (In reply to comment #8)
> > > (In reply to comment #7)
> > > > 1 frame frame extract from the fuzz'd file which causes a crash in
> > > > file.c: cf_read() in the ENDTRY statement (with SVN #45821).
> > >
> > > The exception code is pretty mature at this point,
> > > so I'm not sure why it would suddenly be causing
> > > problems.
> >
> > Well I was playing with moving TRY ... ENDTRY blocks in file.c [to get rid of
> > volatile] some revision ago, but it's IMHO unrelated.
>
> 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.
On Windows it should be catched by __try { } __except { } blocks in
packet-frame.c,
TRY { } ENDTRY { } blocks are wireshark exception handler, where access to
invalid memory is not handled.
> I'll dig into this a bit further.
Maybe _MSC_VER is not defined in your build?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
