Bug 27892 - Want memory view to show memory as disassembly
Summary: Want memory view to show memory as disassembly
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 2.0   Edit
Hardware: PC Linux-GTK
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
: 118231 170980 (view as bug list)
Depends on:
Blocks:
 
Reported: 2002-12-07 16:43 EST by Johan Walles CLA
Modified: 2020-09-04 15:26 EDT (History)
6 users (show)

See Also:

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 Johan Walles CLA 2002-12-07 16:43:08 EST 
The memory view supports showing memory as different sized words, decimal ints
and ascii.  In addition to these, I would like to be able to view memory as
disassembly.
Comment 1 Kleo Hapitas CLA 2004-07-07 16:53:36 EDT 
PR was not targeted to any particular release. Changing target milestone to 2.1
Comment 2 Oyvind Harboe CLA 2004-11-07 15:07:45 EST 
Similarly it would be nice to be able to specify disassembly region by e.g. 
right clicking in the disassembly view.

Not being able to disassemble random memory regions is a bit limiting, 
especially when debugging code that where no debug info is available.

I can't even type in the command manually in the GDB console since CDT eats 
the output:

-----
disassemble 0x100002f0 0x10000306
Dump of assembler code from 0x100002f0 to 0x10000306:
<---- output is missing ---->
End of assembler dump.
----

Expected result:

(gdb) disassemble 0x100002f0 0x10000306
Dump of assembler code from 0x100002f0 to 0x10000306:
0x100002f0 <sort+463>:  pushsp
0x100002f1 <sort+464>:  im 12
0x100002f2 <sort+465>:  add



Øyvind
Comment 3 Nobody - feel free to take it CLA 2004-11-15 11:27:09 EST 
Can be done by using the rendering feature of the platform Memory view. Moving 
the target milestone to 3.0.
Comment 4 Oyvind Harboe CLA 2004-11-30 08:50:07 EST 
An alternative would be to make it possible to enter disassembly range in the
disassembly view.

Øyvind
Comment 5 Oyvind Harboe CLA 2004-11-30 08:53:38 EST 
Also this could fix another problem(rather than opening a new PR, I'm amending
this one):

It should be possible to press the up/down-arrow in the disassembly view and
have the disassembly view disassemble the next region.

E.g. if the debugger comes out of the running state on a SEGFAULT in an area
without debug information/source, it would be nice to view the instructions
preceding the instruction that failed.

Øyvind
Comment 6 Johan Walles CLA 2004-11-30 16:32:18 EST 
Øyvind (and others), please see related bug 27217 and bug 27239.

They might be what you're really looking for.  This bug is only about getting
disassembly in the memory view.
Comment 7 Nobody - feel free to take it CLA 2005-06-10 11:23:40 EDT 
Deferred.
Comment 8 Nobody - feel free to take it CLA 2005-10-07 13:10:01 EDT 
*** Bug 111711 has been marked as a duplicate of this bug. ***
Comment 9 Nobody - feel free to take it CLA 2005-11-28 10:54:17 EST 
*** Bug 118231 has been marked as a duplicate of this bug. ***
Comment 10 Nobody - feel free to take it CLA 2007-01-19 05:27:46 EST 
*** Bug 170980 has been marked as a duplicate of this bug. ***
Comment 11 Jonah Graham CLA 2019-12-30 18:55:37 EST 
This bug was assigned and targeted at a now released milestone (or Future or Next that isn't being used by CDT). As that milestone has now passed, the milestone field has been cleared. If this bug has been fixed, please set the milestone to the version it was fixed in and mark the bug as resolved.