Bug ID |
12611
|
Summary |
VITA 49 Fractional timestamp being read in as a double, when it should be an unsigned 64 bit number
|
Product |
Wireshark
|
Version |
1.10.6
|
Hardware |
x86
|
OS |
All
|
Status |
UNCONFIRMED
|
Severity |
Minor
|
Priority |
Low
|
Component |
Dissection engine (libwireshark)
|
Assignee |
[email protected]
|
Reporter |
[email protected]
|
Created attachment 14718 [details]
Vita 49 Standard
Build Information:
wireshark 1.10.6 (v1.10.6 from master-1.10)
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 GTK+ 3.10.7, with Cairo 1.13.1, with Pango 1.36.1, with
GLib 2.39.91, with libpcap, with libz 1.2.8, with POSIX capabilities (Linux),
without libnl, with SMI 0.4.8, with c-ares 1.10.0, with Lua 5.2, without
Python,
with GnuTLS 2.12.23, with Gcrypt 1.5.3, with MIT Kerberos, with GeoIP, with
PortAudio V19-devel (built Feb 25 2014 21:09:53), with AirPcap.
Running on Linux 3.16.0-76-generic, with locale en_US.UTF-8, with libpcap
version 1.5.3, with libz 1.2.8, GnuTLS 2.12.23, Gcrypt 1.5.3, without AirPcap.
Intel(R) Core(TM) i7-4770 CPU @ 3.40GHz
Built using gcc 4.8.2.
--
In 6.1.5 of the VITA 49 standard (See attached) it reads:
"Each of the three Fractional-seconds Timestamps consists of an unsigned 64-bit
integer which occupies two consecutive 32-bit words."
However for a fractional timestamp value of:
3f f0 00 00 00 00 00 00 (This is the hex for 1 when read as a double)
Wireshark reads it in as 1 instead of the 4607182418800017408 which I expect
You are receiving this mail because:
- You are watching all bug changes.