Wireshark-bugs: [Wireshark-bugs] [Bug 6833] Buildbot crash output: fuzz-2012-02-10-14752.pcap

Date: Sat, 11 Feb 2012 19:03:27 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=6833

Guy Harris <guy@xxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|DUPLICATE                   |WORKSFORME

--- Comment #2 from Guy Harris <guy@xxxxxxxxxxxx> 2012-02-11 19:03:26 PST ---
Bug 6827 and its dups were the result of doing some debugging to figure out why
some buildbot failures weren't causing bugs to be filed; this bug was one of
those failures, and was manually shoved through the bug reporter after the
pcap-ng debug stuff was removed (the bug reporter was apparently running out of
memory, perhaps due to the debugging stuff).

So this probably isn't a dup of 6827.  4294967110 is 0xFFFFFF46, and the byte
sequence FF FF FF 46 *does* appear in the capture.  I put a debugging hack in
to try to catch a named field having the value 0xFFFFFF46, but didn't find any;
whether that's because it's not a named field being used as a length, or
because the allocation was done before the field was put into the protocol
tree, or because the current trunk has the bug "fixed" as a result of some
change e.g. causing the dissector to fail before it gets there, or what, I
don't know.  Closing as WORKSFORME for now; we'll see if it pops up again.

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