Wireshark mailing list archives
Re: Malformed Packet
From: "Ewgenij Sokolovski" <ewgenijkkg () gmx de>
Date: Mon, 14 Jan 2013 12:46:10 +0100
For the more normal case where we try to fetch more bytes than are there, I don't know. If its a protocol I'm working with I can usually quickly tell what has gone wrong, helped by by seeing where dissection stopped.
Hmm, I'm quite new to debugging Wireshark dissectors. So, suppose I see that my dissector stops at point X. The only way to find out what the reason is is to look at the values displayed by Wireshark, compare them with values which were sent in the reality and find the point where dissection went wrong then. Do I understand it right? BR Ewgenij ___________________________________________________________________________ Sent via: Wireshark-users mailing list <wireshark-users () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-users Unsubscribe: https://wireshark.org/mailman/options/wireshark-users mailto:wireshark-users-request () wireshark org?subject=unsubscribe
Current thread:
- Re: Malformed Packet, (continued)
- Re: Malformed Packet Guy Harris (Jan 10)
- Re: Malformed Packet Ewgenij Sokolovski (Jan 10)
- Re: Malformed Packet Guy Harris (Jan 11)
- Re: Malformed Packet Ewgenij Sokolovski (Jan 11)
- Re: Malformed Packet Anders Broman (Jan 11)
- Re: Malformed Packet Ewgenij Sokolovski (Jan 11)
- Re: Malformed Packet Guy Harris (Jan 11)
- Re: Malformed Packet Martin Mathieson (Jan 11)
- Re: Malformed Packet Ewgenij Sokolovski (Jan 14)
- Re: Malformed Packet Martin Mathieson (Jan 14)
- Re: Malformed Packet Ewgenij Sokolovski (Jan 14)
- Re: Malformed Packet Martin Mathieson (Jan 14)
- Re: Malformed Packet Ewgenij Sokolovski (Jan 10)
- Re: Malformed Packet Guy Harris (Jan 10)