Wireshark mailing list archives
Re: Problems with bitmasks and 64 bit values
From: Guy Harris <guy () alum mit edu>
Date: Sun, 30 Oct 2016 14:54:12 -0700
On Oct 30, 2016, at 2:39 PM, Thomas Wiens <th.wiens () gmx de> wrote:
1) It seems to be impossible to decode a value inside the bitmask as signed integer The "Error code" value should be 16 bit signed integer.
But you said it was a 64-bit unsigned integer: { "Error code", "s7comm-plus.returnvalue.errorcode", FT_UINT64, BASE_HEX, NULL, 0x000000000000ffff, NULL, HFILL }}, Try saying it's a 16-bit signed integer - FT_INT16 - instead. Note, however, that we don't support showing negative octal or hex values; if you want it to show up as a signed value, display it with BASE_DEC or BASE_HEX_DEC. ___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev () wireshark org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://www.wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-request () wireshark org?subject=unsubscribe
Current thread:
- Problems with bitmasks and 64 bit values Thomas Wiens (Oct 30)
- Re: Problems with bitmasks and 64 bit values Pascal Quantin (Oct 30)
- Re: Problems with bitmasks and 64 bit values Thomas Wiens (Oct 30)
- Re: Problems with bitmasks and 64 bit values Pascal Quantin (Oct 31)
- Re: Problems with bitmasks and 64 bit values Thomas Wiens (Oct 31)
- Re: Problems with bitmasks and 64 bit values Thomas Wiens (Oct 31)
- Re: Problems with bitmasks and 64 bit values Pascal Quantin (Oct 31)
- Re: Problems with bitmasks and 64 bit values Thomas Wiens (Oct 30)
- Re: Problems with bitmasks and 64 bit values Pascal Quantin (Oct 30)
- Re: Problems with bitmasks and 64 bit values Thomas Wiens (Oct 30)