Wireshark-bugs: [Wireshark-bugs] [Bug 11832] New: Time calculation incorrect when changing filte
Date: Mon, 30 Nov 2015 17:38:48 +0000
Bug ID 11832
Summary Time calculation incorrect when changing filters and using time since previously displayed packet
Product Wireshark
Version 2.0.0
Hardware x86
OS Windows 7
Status UNCONFIRMED
Severity Major
Priority Low
Component Dissection engine (libwireshark)
Assignee bugzilla-admin@wireshark.org
Reporter fischmarket@outlook.com

Created attachment 14094 [details]
Screenshots of the problem

Build Information:
Version 2.0.0 (v2.0.0-0-g9a73b82 from master-2.0)

Copyright 1998-2015 Gerald Combs <gerald@wireshark.org> 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) i5-4300U CPU @ 1.90GHz (with SSE4.2), with 8089MB of physical
memory.


Built using Microsoft Visual C++ 12.0 build 31101

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

Check the man page and http://www.wireshark.org for more information.
--
There seems to be a bug with 2.0.0 with time since previously displayed packet.
When I follow TCP stream while selecting a packet with a 1.2 second time since
previously displayed packet, that time incorrectly shows up as 1.2 seconds
after the tcp stream filter is applied which is not right. See my attachment
for more infomation.


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