Wireshark-bugs: [Wireshark-bugs] [Bug 11297] New: 802.11 TX Rate sorting issue

Date: Mon, 22 Jun 2015 20:39:00 +0000
Bug ID 11297
Summary 802.11 TX Rate sorting issue
Product Wireshark
Version 1.12.6
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component GTK+ UI
Assignee [email protected]
Reporter [email protected]

Created attachment 13682 [details]
Capture file to show the sorting issue

Build Information:
Version 1.12.6 (v1.12.6-0-gee1fce6 from master-1.12)

Copyright 1998-2015 Gerald Combs <[email protected]> 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 (64-bit) with GTK+ 2.24.23, with Cairo 1.10.2, with Pango 1.34.0, with
GLib 2.38.0, with WinPcap (4_1_3), with libz 1.2.5, with SMI 0.4.8, with c-ares
1.9.1, with Lua 5.2, without Python, with GnuTLS 3.2.15, with Gcrypt 1.6.2,
without Kerberos, with GeoIP, with PortAudio V19-devel (built Jun 17 2015),
with
AirPcap.

Running on 64-bit Windows 7 Service Pack 1, build 7601, with WinPcap version
4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version 1.0 branch
1_0_rel0b (20091008), GnuTLS 3.2.15, Gcrypt 1.6.2, with AirPcap 4.1.3 build
3348.
      Intel(R) Core(TM) i7-2630QM CPU @ 2.00GHz, with 12265MB of physical
memory.


Built using Microsoft Visual C++ 10.0 build 40219

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

Check the man page and http://www.wireshark.org for more information.
--
I use a custom column using '802.11 TX Rate' and when sorting it, it partially
failed. Basically, you can see rates from 12 to 54. Then, 6.0 and 6.5 were
added after 54.

It feels like sorting might be done using strings when in this case, it should
be done as a floating point number.


You are receiving this mail because:
  • You are watching all bug changes.