[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [cdt-dev] Disassembly in memory view?
|
John,
I think a quick and simple implementation
of the disassembly rendering can be added regardless of what I am
doing. I also think the current API is sufficient.
Mikhail
Mikhail, didn't realize the disassembly work you were doing (sort of
:-) ) also involved a memory rendering. Disregard my previous
email.
John
At 09:58 AM 5/29/2009, Mikhail Khodjaiants wrote:
Content-class:
urn:content-classes:message
Content-Type:
multipart/alternative;
boundary="----_=_NextPart_001_01C9E06D.DF994372"
Doug,
It has been in the
requirements for disassembly for a long time. The implementation I am working
on (sort of) has it (see plugin.xml for debug.ui). In fact the same viewer is
used in the editor and the rendering. I thought I mentioned it during my
presentation at the summit, but I am not sure about it
now.
Mikhail
From: cdt-dev-bounces@xxxxxxxxxxx [
mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug
Schaefer
Sent: Friday, May 29, 2009 3:37 PM
To: CDT
General developers list.
Subject: [cdt-dev] Disassembly in memory
view?
Hey guys,
Something crossed my mind looking at the
memory view today. Have discussed whether we could do disassembly as a memory
rendering? Not sure it makes sense there. When testing it out, I grabbed the
only memory address I could find, i.e. the address on the stack at the initial
breakpoint inside main. I thought it would be cool to see the disassembly at
that point. Just a crazy thought.
Doug.
--
IMPORTANT
NOTICE: The contents of this email and any attachments are confidential and
may also be privileged. If you are not the intended recipient, please notify
the sender immediately and do not disclose the contents to any other person,
use it for any purpose, or store or copy the information in any medium. Thank
you.
_______________________________________________
cdt-dev mailing
list
cdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-dev
--
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.