Bug ID |
9014
|
Summary |
crashes with option "-z io,stat,..." in the presence of negative relative packet timestamps
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.10.1
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
TShark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
TShark 1.10.1 (SVN Rev 50926 from /trunk-1.10)
Copyright 1998-2013 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 (32-bit) with GLib 2.34.1, with WinPcap (4_1_3), with libz 1.2.5,
without POSIX capabilities, without libnl, with SMI 0.4.8, with c-ares 1.9.1,
with Lua 5.1, without Python, with GnuTLS 2.12.18, with Gcrypt 1.4.6, with MIT
Kerberos, with GeoIP.
Running on 32-bit Windows 7 Service Pack 1, build 7601, without WinPcap.
Intel(R) Core(TM)2 Extreme CPU Q9300 @ 2.53GHz, with 3571MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Running the command
tshark -z "io,stat,0,tcp.srcport" -r example.pcap
crashes in case the pcap file contains a packet timestamp where the relative
timestamp from the beginning of the capture is negative.
This was working with tshark version 1.8.3 and seems to be broken in 1.8.4 and
upwards.
You are receiving this mail because:
- You are watching all bug changes.