Wireshark-bugs: [Wireshark-bugs] [Bug 3216] mysql : fix for "FIXME: write mysql_dissect_row_pack
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Sun, 1 Mar 2009 13:41:01 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3216


Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jeff.morriss.ws@xxxxxxxxx
             Status|NEW                         |RESOLVED
         Resolution|                            |FIXED




--- Comment #4 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx>  2009-03-01 13:41:00 PDT ---
(In reply to comment #2)
> I'm wondering whether the internal logic of the mysql dissector produces
> different results if called from tshark versus called from wireshark w/ respect
> to the settings if packet details should be shown.

I noticed that how the dissector was dissecting the frames varied based on the
order of my clicks, too.

It looks like the state management tracking was fixed in rev 22339 but broken
again in 25728.  Anyway I fixed it (and cleaned it up some) in 27575.


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