https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5755
--- Comment #6 from Chris Maynard <christopher.maynard@xxxxxxxxx> 2011-03-16 08:02:46 PDT ---
(In reply to comment #3)
> Although this corrected alternate patch does work, it looses the discrimination
> between the length, and the string itself. After developing an AgentX support
> library, I found this additional information (break-out) useful, the
> FT_UINT_STRING technique requires the user to 'understand' that they are
> looking at a 4-byte-length encoded something, whereas the old approach provided
> that additional clue.
I wonder if changing the display of FT_UINT_STRING would be useful nonetheless
so that instead of only displaying the string, the number of bytes is
[pre|app]ended?
For example, given this FT_UINT_STRING, (where the length field is 4 bytes in
Big-Endian byte order):
00 00 00 0c 48 65 6c 6c 6f 20 57 6f 72 6c 64 21
Instead of displaying:
The string: Hello World!
Display something like this:
The string: (12 bytes) Hello World!
Or this:
The string: Hello World! (12 bytes)
?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
