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


I think that the idea was to genearate a read-only file for each debug
session. This file would be created using the object file and found
source files at the beginning of the debug session and it would be
destroyed at the end. The original source file would not actually be


-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Mikhail Khodjaiants
Sent: Friday, May 12, 2006 1:35 PM
To: CDT General developers list.
Subject: 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
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>;
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
> would rapidly toggle between these as they stepped through code.
> We also added the same functionality to our memory view so you could
> any address and view disassembly, mixed, or source. Of course the
> two
> were only available if the address happened to have source
> In both the editor and memory views the underlying implementation was
> same.
> If you wanted to edit the source while debugging the source file would
> cloned. A static snapshot would be cached for use by the debugger and
> original edited normally. I've wondered if the "local history"
> could be leveraged for this but have never looked into it. Of course
> 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
>> Hi,
>> I propose starting a new thread for future communications about the
>> Debug Model since there's a technology subgroup in the DSDP-DD.  I
>> like to leave this thread for Editor enhancement/ideas/requests
>> on embedded development.
>> Thanks,
>> Ewa.
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx

cdt-dev mailing list

Back to the top