Wireshark-bugs: [Wireshark-bugs] [Bug 4860] New: Crash triggered when changing display filter fr
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Wed, 9 Jun 2010 13:33:29 -0700 (PDT)
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=4860

           Summary: Crash triggered when changing display filter from
                    right-mouse pop-up menu via packet-list
           Product: Wireshark
           Version: SVN
          Platform: Other
        OS/Version: Windows XP
            Status: NEW
          Severity: Major
          Priority: Medium
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: jyoung@xxxxxxx


Build Information:
Version 1.5.0-SVN-33184 (SVN Rev 33184 from /trunk)

Copyright 1998-2010 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.16.6, (32-bit) with GLib 2.22.4, with WinPcap (version
unknown), with libz 1.2.3, without POSIX capabilities, without libpcre, with
SMI
0.4.8, with c-ares 1.7.1, with Lua 5.1, without Python, with GnuTLS 2.8.5, with
Gcrypt 1.4.5, with MIT Kerberos, with GeoIP, with PortAudio V19-devel (built
Jun
 9 2010), with AirPcap.

Running on Windows XP Service Pack 3, build 2600, with WinPcap version 4.1.1
(packet.dll version 4.1.0.1753), based on libpcap version 1.0 branch 1_0_rel0b
(20091008), GnuTLS 2.8.5, Gcrypt 1.4.5, with AirPcap 4.1.0 build 1622.

Built using Microsoft Visual C++ 9.0 build 30729

Wireshark is Open Source Software released under the GNU General Public
License.

Check the man page and http://www.wireshark.org for more information.

--
The attached trivial trace file can be used to demonstrate the following
problem.

Changing a display filter by using the right mouse pop-up menu via
packet-list can trigger Wireshark to crash.

Steps to reproduce:

1: Open up the attached trace file in Wireshark.

2: Enter a display filter of "arp".   4 frames should be listed 1-2 and 11-12.

3: In the packet list put the cursor over frame 11 (or 12) and the "Source"
column and then enter a right mouse click.  The targeted frame (11 or 12) show
be selected and a pop-up menu should be displayed.

4: From the pop-up menu select either the "Apply as Filter" or "Select as
Filter" menu items and then select any of their sub-menu options (for example
"Selected").  This will trigger crash.

The problem appears to be related to having a display filter in place that and
then triggering the pop-up from a later frame from the packetlist.   The crash
does not appear to happen if the pop-up is triggered from the packet details. 

NOTE: If you choose frames 1 or 2 instead of 11 or 12 in step 3 you will NOT
trigger the crash.

A similar crash can be triggered by setting an initial display filter of:

   "frame.number == 1 || frame.number == 3"

And then right mouse clicking on frame 3 Source column in the packet list and
select either the "Apply as Filter" or "Select as Filter" submenu options.

I have also replicated issue with a very recent SVN 33194 built locally.

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