Wireshark-bugs: [Wireshark-bugs] [Bug 11042] dissection not happening properly for latitude and

Date Prev · Date Next · Thread Prev · Thread Next
Date Index · Thread Index · Other Months · All Mailing Lists
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Fri, 13 Mar 2015 20:16:17 +0000

changed bug 11042


What Removed Added
Status INCOMPLETE RESOLVED
Resolution --- NOTABUG

Comment # 7 on bug 11042 from 
The fix that corrects the display to show 21.701904 and 23.701904 - which are,
as per my analysis, the correct values, *NOT* 21.23... or 23.23... - was in
1.99.3, but was not in the 1.99.2 release.  It was made on February 28, 2015.

Change 7592d39 is older; it was made on December 13, 2014, so
1.99.2-35-g7592d39 might not show the correct values.

Please update all your machines either to the 1.99.3 development release or to
a *later* version.

If anybody at your company believes that the correct fractional part of the
longitude and latitude values is .23... rather than .701904, please have them
provide a document indicating that the correct interpretation of "a two's
complement, fixed point number with 9 whole bits" in RFC 6757, section 3.1.2,
is *not* that the number is a binary number with the binary point following the
first 9 bits of the number.

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