Bug ID |
10213
|
Summary |
extra quotes around date fields (FT_ABSOLUTE_TIME) when using -E quote=d or s
|
Classification |
Unclassified
|
Product |
Wireshark
|
Version |
1.12.0
|
Hardware |
x86
|
OS |
Windows 7
|
Status |
UNCONFIRMED
|
Severity |
Major
|
Priority |
Low
|
Component |
TShark
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Build Information:
TShark 1.12.0-rc2 (v1.12.0-rc2-0-gfd017ee from master-1.12)
Copyright 1998-2014 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 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.1.22,
with Gcrypt 1.6.0, without Kerberos, with GeoIP.
Running on 64-bit Windows 7 Service Pack 1, build 7601, without WinPcap.
Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz, with 2047MB of physical
memory.
Built using Microsoft Visual C++ 10.0 build 40219
--
Correct output from tshark 1.10.7 & 1.11.3:
tshark -T fields -e frame.len -e frame.time -E quote=d
"80" "Jun 20, 2014 19:32:35.394428000"
"112" "Jun 20, 2014 19:32:35.442770000"
Incorrect output from tshark 1.10.8 & 1.12.0-rc2:
tshark -T fields -e frame.len -e frame.time -E quote=d
"42" ""Jun 20, 2014 21:32:17.084782000 Coordinated Universal Time""
"60" ""Jun 20, 2014 21:32:17.084868000 Coordinated Universal Time""
Notice the doubly-quoted double quotes around the time field in the second
example above. When using -E quote=s, tshark will output '"Jun 20, 2014
21:42:53.439193000 Coordinated Universal Time"'. This happens for any
FT_ABSOLUTE_TIME field, not just frame.time. This error seems to coincide with
the changing of the formatting of that field to include the fully-spelled out
time zone name.
You are receiving this mail because:
- You are watching all bug changes.