Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] RE: [dsdp-dd-dev] Editor technology subgroup

There is at least one problem in Eclipse with having disassembly embedded in the editor. If you run two debug sessions using the same source file on different platforms, the disassembly is different for each platform. So your editor has to react to context changes and insert the right disassembly.

----- Original Message ----- From: "Ken Ryall" <ken.ryall@xxxxxxxxx> To: "Device Debugging developer discussions" <dsdp-dd-dev@xxxxxxxxxxx>; "CDT General developers list." <cdt-dev@xxxxxxxxxxx>
Sent: Friday, May 12, 2006 4:16 PM
Subject: Re: [cdt-dev] RE: [dsdp-dd-dev] Editor technology subgroup

My feedback on the editor experience while debugging:

The editor in our legacy tools lets you switch between source, disassembly,
and mixed in the same view. People really like this and some developers
would rapidly toggle between these as they stepped through code.

We also added the same functionality to our memory view so you could pick
any address and view disassembly, mixed, or source. Of course the latter two
were only available if the address happened to have source correspondence.
In both the editor and memory views the underlying implementation was the

If you wanted to edit the source while debugging the source file would be
cloned. A static snapshot would be cached for use by the debugger and the
original edited normally. I've wondered if the "local history" mechanism
could be leveraged for this but have never looked into it. Of course the
next time you rebuild the executable the cached version of the file is
tossed and the current one used again.

Our developers are used to this functionality and we will likely need
something similar in our new tools as well.

Thanks - Ken

From: ext Ewa Matejska <Ewa.Matejska@xxxxxxxxxxxxxx>
Reply-To: Device Debugging developer discussions <dsdp-dd-dev@xxxxxxxxxxx>
Date: Fri, 12 May 2006 11:42:55 -0700
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>, Device Debugging
developer discussions <dsdp-dd-dev@xxxxxxxxxxx>
Conversation: [cdt-dev] RE: [dsdp-dd-dev] Editor technology subgroup
Subject: RE: [cdt-dev] RE: [dsdp-dd-dev] Editor technology subgroup


I propose starting a new thread for future communications about the
Debug Model since there's a technology subgroup in the DSDP-DD.  I would
like to leave this thread for Editor enhancement/ideas/requests focusing
on embedded development.


cdt-dev mailing list

Back to the top