Wireshark-bugs: [Wireshark-bugs] [Bug 1159] New: Wireshark packet-list pane not displayed/update
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1159
Summary: Wireshark packet-list pane not displayed/updated
correctly after two empty display filters
Product: Wireshark
Version: SVN
Platform: PC
OS/Version: Windows XP
Status: NEW
Severity: Minor
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: jyoung@xxxxxxx
Build Information:
Version 0.99.4-SVN-19500 (SVN Rev 19500)
Copyright 1998-2006 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.6.9, with GLib 2.6.6, with WinPcap (version unknown),
with libz 1.2.3, with libpcre 6.4, with Net-SNMP 5.3.1, with ADNS, with Lua
5.1,
with GnuTLS 1.5.1, with Gcrypt 1.2.3, with MIT Kerberos, with PortAudio <= V18.
Running on Windows XP Service Pack 1, build 2600
with WinPcap version 3.1 (packet.dll version 3, 1, 0, 27), based on libpcap
version 0.9[.x].
Wireshark is Open Source Software released under the GNU General Public
License.
Check the man page and http://www.wireshark.org for more information.
--
Hello,
Wireshark will get into a state where the packet list pane will not
update properly if one enters two consecutive "empty display filters"*
and then clears the second display filter. After clearing the second
display filter the packet list pane should display all packets but does
not.
* By "empty display filter" I mean a display filter that will result in zero
matching frames.
o How to reproduce problem:
Open a simple trace file (for example a trace file that contains only
ICMP "ping" packets (see attached trace)).
Enter the display filter "rpc" and you will have an empty packet
list.
Replace the "rpc" display filter with the display filter "nfs" and
you will again have an empty packet list.
Now clear the display filter.
The packet-list pane itself will not be displayed correctly (most likely it
will appear empty) but the packet detail pane and the hex view pane
will display details of the 1st packet.
Once in this state you can still scroll through the (now invisible)
list of packets and the packet details pane and the hex view panes
will update as new packets are invisibly selected.
If you minimize and restore Wireshark, or if you move another window
over the packet list pane you can usually get the packet-list entries
to appear. But the packet list itself will NOT update nor scroll as you
move through the list of packets.
o How to undo the problem:
You can restore normal packet-list display functionality without
completely restarting Wireshark by doing the following:
Close the current trace file.
(Re)open a trace file.
Enter a display filter that you know WILL result in displaying some
packets (i.e. "frame").
Now clear the display filter.
The packet-list pane will then behave normally.
o When did problem first appear?
I've gone back tested with several Buildbot versions that I had
available and determined that the problem did NOT appear
in Buildbot version SVN 15354 or in earlier versions.
With Buildbot version 15805 I did have a related assertion error
on line 789 of file gtk/packet_list.c when I entered a display filter
that resulted in an empty packet list.
> ** ERROR **: file packet_list.c: line 789: assertion failed:
> (eth_clist_row_is_visible(ETH_CLIST(packet_list), row) == GTK_VISIBILITY_FULL)
> aborting…
A fix for this assertion error was introduced in SVN 15829 (Thursday,
Sep. 15, 2005) and quickly amended in SVN 15830 (Friday, Sep. 16, 2005).
But I suspect that the current packet list problem has been present since
then.
I have seen the current packet list display problem from virtually all Buildbot
versions from 0.10.12.SVN-15843 through the most recent 0.99.4-SVN-19500.
I initially saw the problem on the Windows XP systems, but a colleague at
work confirmed that he has the same packet list problem with Wireshark
running on his SUSE Linux system.
Given the way the packet list pane behaves when the problem is present
would this be a clist freeze/thaw imbalance within gtk/packet_list.c?
I hope you find this information useful.
Sincerely,
Jim Young
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
