Bug 562885

Summary: Hexdump Detail Formatter for byte[]
Product: [Eclipse Project] JDT Reporter: Juergen Weber <juergen>
Component: DebugAssignee: JDT-Debug-Inbox <jdt-debug-inbox>
Status: NEW --- QA Contact:
Severity: normal    
Priority: P3 CC: sarika.sinha, stephan.herrmann
Version: 4.16Keywords: helpwanted
Target Milestone: ---   
Hardware: PC   
OS: Windows 10   
Whiteboard:
Attachments:
Description Flags
Hex View of CDT none

Description Juergen Weber CLA 2020-05-06 10:09:01 EDT 
In the debugger variables view it should be possible to display a byte[] as  Canonical hex+ASCII display (Linux hexdump -C).

E.g. instead of

[71, 73, 79, 80, 1, 2]

it should display

47 49 4f 50 01 02   GIOP..


See also:

https://www.eclipse.org/forums/index.php/m/1826899/

https://stackoverflow.com/questions/3939461/how-do-i-display-a-byte-array-as-an-array-of-hex-bytes-or-unsigned-decimal-number

https://stackoverflow.com/questions/381546/how-can-i-display-a-byte-array-as-a-string-in-javas-debug-detail-formatter/381934

https://bugs.eclipse.org/bugs/show_bug.cgi?id=187922
Comment 1 Stephan Herrmann CLA 2020-05-07 08:34:12 EDT 
From a UI perspective, I wonder which approach would be better:

As a (predefined?) detail formatter? (Note that "byte[]" can currently not be used). This would be quite flexible but might require some additional effort to integrate a predefined detail formatter.

Or in the display settings for primitive types? This would slightly bend the interpretation of "primitive" but would probably be easiest to implement.


@Team: any preferences?
Comment 2 Sarika Sinha CLA 2020-05-07 08:58:23 EDT 
Anyone interested in providing the support?
Comment 3 Juergen Weber CLA 2020-05-07 10:50:13 EDT 
Created attachment 282743 [details]
Hex View of CDT

CDT's debugger has a hexview, but not very nice, as each byte is on a new line.
Comment 4 Eclipse Genie CLA 2022-04-28 08:42:39 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 5 Juergen Weber CLA 2022-07-12 10:18:31 EDT 
Still relevant.