Wireshark-bugs: [Wireshark-bugs] [Bug 2225] New: Incorrect behavior using sorting in the packet
http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=2225
Summary: Incorrect behavior using sorting in the packet list
Product: Wireshark
Version: SVN
Platform: All
OS/Version: Mac OS X 10.5
Status: NEW
Severity: Normal
Priority: Low
Component: Wireshark
AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
ReportedBy: stig@xxxxxxxxxxxxx
Build Information:
Paste the COMPLETE build information from "Help->About Wireshark", "wireshark
-v", or "tshark -v".
--
1. The selected row in the packet list does change in rescan_packets() when the
packet list is not sorted by package number.
The fix in r20394 for bug 1140 breaks the functionality for selecting the
previous selected row when the list is not sorted by package number (or time).
Try sorting on the Info column, select a package and toggle coloring. Watch
which package is selected.
This happens because in rescan_packets() because we first reload all packages
in order and find the selected package row number. We then re-sort the list
using the previously selected order, and now the row number we found does not
match the correct package in the re-sorted list.
Another issue is that we do packet_list_freeze and package_list_thaw in
packet_list_set_sort_column() while we already are in a list_freeze.
2. When selecting a row in the package list and changing the sort order the
selected row may not be in the current view.
3. When capturing, the new packages are always appended to the list, and not
put in correct sorting order. This is done correctly in conversations and
endpoints.
--
Configure bugmail: http://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
