Wireshark mailing list archives
Re: Incorrect decoding at first time, then filtering at the second time corrects the decoding
From: Christopher Maynard <Chris.Maynard () gtech com>
Date: Wed, 8 Dec 2010 16:15:48 +0000 (UTC)
Vishal Kumar Singh <vishal.ismdh@...> writes:
Hi All,In wireshark, I am trying to decode a packet by taking its information
from the last decoded packet (Control packet and Data Packet). In the first time, few data packet takes wrong information and, decodes the packet accordingly. When I mark the faulty packet and clear the filter, the decoding of faulty packet becomes good. What should be the reason behind this? Please, help me out.regards,Vishal Kumar Singh Just a guess, but you may have some code surrounded by an "if (tree) { ... }" block that shouldn't be. If you have any "if (tree)"'s in your code, temporarily try replacing them with "if (1)" to see if it makes any difference. If it does, you can either leave it that way or figure out which parts need to be called regardless of tree being NULL or not. Review the skeleton code in section 1.2 of doc/README.developer for more guidelines. If this isn't your problem, then you might consider posting your code if you can. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Incorrect decoding at first time, then filtering at the second time corrects the decoding Vishal Kumar Singh (Dec 07)
- Re: Incorrect decoding at first time, then filtering at the second time corrects the decoding Stephen Fisher (Dec 08)
- Re: Incorrect decoding at first time, then filtering at the second time corrects the decoding Christopher Maynard (Dec 08)