Bug 4669 - Should memory window table elements include 0x?
Summary: Should memory window table elements include 0x?
Status: RESOLVED FIXED
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Unassigned
URL:
Keywords:
Depends on:
Blocks: 3119
  Show dependency tree / graph
 
Reported: 2007-06-20 16:26 UTC by Andrew Cagney
Modified: 2007-09-26 07:47 UTC (History)
0 users

See Also:
Host:
Target:
Build:
Last reconfirmed:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2007-06-20 16:26:14 UTC 
This came up in discussion in 2007-06-20 meeting; I'm not clear that it was
resolved fully.  It was noted that the default should be: location, byte, "word
in natural byte order", I assume that in the below:

Should memory window table elements include 0x?

For instance:
  0x00000000 | 01 02 03 04 | 04030201
vs:
  0x00000000 | 0x01 0x02 0x03 0x04 | 0x04030201
vs:
  0x00000000 | 01 02 03 04 | 0x04030201

My take is that the third should be the default:

-> fixed sized hex quantities (8, 16, ...) dropped the 0x
-> "word" sized hex quantities included it

For instance
             | 8-bit       | 16-bit BE | Word BE
  0x00000000 | 01 02 03 04 | 0102 0304 | 0x01020304
Comment 1 Zhao Shujing 2007-09-26 07:47:31 UTC 
After investigate gdb gtk/insight and other debuggers of linux, Choose the
second one to frysk.
2007-09-25  Zhao Shujing <pearly.zhao@oracle.com>

        * memory/MemoryWindow.java: Fixes #4674.
        * gladedir/memorywindow.glade: Change adjustment to eight.