Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

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

Date: Thu, 19 Nov 2009 23:40:14 -0800 (PST)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4254

           Summary: Warn Dissector bug, protocol ADATA, in packet 372: More
                    than 1000000 items in the tree -- possible infinite loop
           Product: Wireshark
           Version: 1.2.4
          Platform: Other
        OS/Version: SuSE
            Status: NEW
          Severity: Blocker
          Priority: High
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: mformaninder@xxxxxxxxx


Build Information:
wireshark --version
wireshark 1.2.4

Copyright 1998-2009 Gerald Combs <gerald@xxxxxxxxxxxxx> and contributors.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Compiled with GTK+ 2.4.13, with GLib 2.4.7, with libpcap 0.8, with libz
1.2.1.2,with POSIX capabilities (Linux), without libpcre, with SMI 0.4.3,
without
c-ares, without ADNS, without Lua, without GnuTLS, with Gcrypt 1.2.0, with MIT
Kerberos, without GeoIP, without PortAudio, without AirPcap.
NOTE: this build doesn't support the "matches" operator for Wireshark filter
syntax.

Running on Linux 2.6.9-55.ELsmp, with libpcap version 0.8, Gcrypt 1.2.0.

Built using gcc 3.4.6 20060404 (Red Hat 3.4.6-3).

--
Hi there,

When I try to run wireshark, I couldn’t successfully capture all the packets.
Wireshark thinks it saw a million items in just one packets and went into an
infinite loop and hogged the machine. 

Warn Dissector bug, protocol ADATA, in packet 372: More than 1000000 items in
the tree -- possible infinite loop.

Can you please provide the solution?


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