ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-bugs: [Wireshark-bugs] [Bug 4254] Warn Dissector bug, protocol ADATA, in packet 372: M

Date: Sun, 22 Nov 2009 22:07:39 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4254


Guy Harris <guy@xxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #5 from Guy Harris <guy@xxxxxxxxxxxx>  2009-11-22 22:07:38 PDT ---
Then perhaps it's a bug in your plugin for that protocol, which, for some
reason, only shows up some of the time.  (Perhaps, with some packets, it really
*does* loop infinitely; make sure, for example, that if you have a sequence of
items in that protocol, and you advance an offset variable through the packet
for each item, the offset is always advanced by at least one byte - don't let
the plugin process the same data over and over and over again in a loop.)

I would suggest that you try to debug your plugin first; then, if you find a
bug in Wireshark itself, file that.


-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.