| Bug ID |
9317
|
| Summary |
The tshark summary line doesn't display the frame number or displays it sporadically.
|
| Classification |
Unclassified
|
| Product |
Wireshark
|
| Version |
SVN
|
| Hardware |
x86-64
|
| OS |
Windows 7
|
| Status |
UNCONFIRMED
|
| Severity |
Normal
|
| Priority |
Low
|
| Component |
TShark
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
Version 1.11.1 (SVN Rev 52797 from /trunk)
Compiled (64-bit) with GTK+ 2.24.14, with Cairo 1.10.2, with Pango 1.30.1, 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, without Kerberos, with GeoIP, with
PortAudio V19-devel (built Oct 21 2013), 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 2.12.18, Gcrypt 1.4.6, without AirPcap.
Intel(R) Core(TM) i5-2540M CPU @ 2.60GHz, with 8072MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 30319
--
tshark.exe -i 4 -c 10 -o "gui.column.format:\"No.\",\"%m\",\"Time\",\"%t\"" -P
produces the following incorrect output:
Capturing on 'Local Area Connection'
0.000000
0.318435
0.811519
0.964782
1.557125
1.604808
2.160022
2.239836
2.963742
3.358373
10 packets captured
Flushing each packet by adding the '-l' option to the above command-line makes
no difference ... however, when the same 2 tests are done with trunk-1.10, I
get, first without flushing:
Capturing on 'Local Area Connection'
10 0.000000
0.199137
0.315498
0.389381
0.518098
0.551330
0.638102
0.638275
0.638400
0.639807
... and then with flushing:
Capturing on 'Local Area Connection'
0.000000
0.094940
0.560227
3 1.051266
1.245360
5 1.581312
1.605920
1.606050
2.001396
9 2.006874
10
With trunk-1.8, the frame numbers are never printed regardless of whether the
packets are flushed or not.
You are receiving this mail because:
- You are watching all bug changes.
