Bug ID |
12401
|
Summary |
Qt Interface clicking on IO graph goes to wrong packet in Packet List
|
Product |
Wireshark
|
Version |
2.0.3
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
GTK+ UI
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 14529 [details]
Capture file with two TCP deltas over 9 seconds.
Build Information:
Version 2.0.3 (v2.0.3-0-geed34f0 from master-2.0)
Copyright 1998-2016 Gerald Combs <[email protected]> and contributors.
License GPLv2+: GNU GPL version 2 or later
<http://www.gnu.org/licenses/old-licenses/gpl-2.0.html>
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 Qt 5.3.2, with WinPcap (4_1_3), with libz 1.2.8, with
GLib 2.42.0, with SMI 0.4.8, with c-ares 1.9.1, with Lua 5.2, with GnuTLS
3.2.15, with Gcrypt 1.6.2, with MIT Kerberos, with GeoIP, with QtMultimedia,
with AirPcap.
Running on 64-bit Windows 7 Service Pack 1, build 7601, with locale C, with
WinPcap version 4.1.3 (packet.dll version 4.1.0.2980), based on libpcap version
1.0 branch 1_0_rel0b (20091008), with GnuTLS 3.2.15, with Gcrypt 1.6.2, without
AirPcap.
Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz (with SSE4.2), with 16300MB of physical
memory.
Built using Microsoft Visual C++ 12.0 build 40629
--
Clicking on plot points on the IO Graph in Qt Wireshark is much less accurate
than in the GTK interface, and does not take one to the correct packet.
To reproduce:
Download the attached trace file, "IO Graph.pcapng." In the GTK interface, go
to the advanced IO graph and plot MAX(*) using field tcp.time_delta. Leave tick
interval at 1 second and other values at their defaults. There are two places
where the TCP delta time rises to almost 10 seconds. Clicking on the two plot
points takes me to packets 1,049 and 7,037 respectively. These are the exact
packets which have the delay.
Now create the same graph in the Qt interface. Clicking on the two high-delay
plot points takes me to packets 1,616 and 7,583, which are several hundred
packets away from the packets that actually have the delay.
Also, having a hand symbol instead of a pointed cursor makes it more difficult
to tell exactly where the click point is.
You are receiving this mail because:
- You are watching all bug changes.