https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2588
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
--- Comment #14 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2010-05-12 11:26:04 PDT ---
(In reply to comment #13)
> FYI ...
>
> Running r32773 on Windows XP SP2, I was looking at the attached capture file
> and noticed some malformed packets. Clicking on frame 32, which is identified
> as being malformed through the expert infos, causes a Wireshark crash. The
> console output shows the following:
>
> 14:13:44 Warn Dissector bug, protocol Line-based text data, in packet
> 32: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
> 14:13:44 Warn Dissector bug, protocol MATE, in packet 32:
> STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
> 14:13:46 Warn Dissector bug, protocol Line-based text data, in packet
> 32: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
> 14:13:46 Warn Dissector bug, protocol MATE, in packet 32:
> STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
> 14:13:48 Warn Dissector bug, protocol Line-based text data, in packet
> 32: STATUS_ACCESS_VIOLATION: dissector accessed an invalid memory address
I don't get any malformed packets nor a crash (on 64-bit Linux).
But: I don't have any MATE scripts configured (and you're seeing errors in MATE
so I'm guessing you have one). Could you share yours (privately, if need-be)?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.