Wireshark-bugs: [Wireshark-bugs] [Bug 11042] dissection not happening properly for latitude and
Date Index · Thread Index · Other Months · All Mailing Lists
Date Prev · Date Next · Thread Prev · Thread Next
From: bugzilla-daemon@xxxxxxxxxxxxx
Date: Mon, 09 Mar 2015 09:09:29 +0000

changed bug 11042


What Removed Added
Status UNCONFIRMED INCOMPLETE
Ever confirmed   1

Comment # 1 on bug 11042 from 
1.99.3 is the current development version.  Please try that version to see
whether it correctly dissects the longitude and latitude.

The code has gone through several changes, not all of which resulted in correct
or  portable code.  The current code is fairly straightforward; it does not
assume that floating-point numbers are IEEE 754-style numbers (they probably
are on most if not all platforms on which Wireshark runs, but it's better not
to assume that), it merely extracts the signed 24-bit fixed-point number,
sign-extends it to a 32-bit signed fixed-point number, and then (implicitly)
converts it to a floating-point number and divides it by 32768 (to scale it
appropriately as per the position of the binary-point).

If there are problems, please attach a capture with a packet containing the
incorrectly-decoded values (not a screenshot, an actual capture file, so we can
see what the raw bits in the field are) and an indication of what the values
should be.

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