Re: [cdt-debug-dev] CDT debugger features

[Samantha Chan <chanskw@xxxxxxxxxx>]

Hi John -

Glad to see some of your requirements for the Memory View.

Re:  a. Toggle endian-ness of memory units
The renderings provided by the platform cannot do this yet.  I filed an
enhancement request for this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=100079

Re:  b. Save, Load and Fill functions
The renderings allow you to copy the content to a clipboard.  You can then
paste it to an editor and save it to a file.
However, the renderings does not export the content nor does it read in a
file for modifying its content.

I filed an enhancement request for this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=100080

Re:  c. View memory as source, mixed, or disassembly.
This needs to be a custom rendering provided by CDT.

Re:  d. View memory as UNICODE.
CDT can provide custom rendering to support this.  It can override
TextRendering and provide UNICODE as the code page for displaying memory
content.

Re: e. Set Watchpoint on memory range.
CDT can contribute actions to renderings to support this.  There may be
problems with allowing user to select multiple cells from the renderings as
the table viewer does not support multi-cell select.

Re:  f. Support address spaces.
I believe there is some support at the platform level.  User can enter any
expression in the "Add Memory Block" dialog and it's up to CDT to interpret
the expression and provide a valid memory block.  CDT can interpret an
expression that includes address space id and return an appropriate memory
block to the Memory View. I also added APIs to allow clients to define a
range for a memory block.  By providing different start/end addresses in a
memory block, clients can separate out the different address spaces.
However, the addresses in the memory blocks are still represented by a
BigInteger.  As discussed in your previous notes, this may not be
sufficient in representing an address.  This may be a problem with actions
like "Go To Address..." as the Memory View assumes that the input is just
an integer and does not take address space into account.

I filed the following enhancement request to track this:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=100081

Thanks...
Samantha



                                                                           
             "Mikhail                                                      
             Khodjaiants"                                                  
             <mikhailk@xxxxxxx                                          To 
             >                         "CDT Debug developers list"         
             Sent by:                  <cdt-debug-dev@xxxxxxxxxxx>         
             cdt-debug-dev-bou                                          cc 
             nces@xxxxxxxxxxx                                              
                                                                   Subject 
                                       Re: [cdt-debug-dev] CDT debugger    
             06/14/2005 04:07          features                            
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
                 CDT Debug                                                 
              developers list                                              
                                                                           
                                                                           




John,

Thanks for your posting, it is very interesting for us. Just a few
comments.

Item 6 (Multiple thread debug context) was dicussed among other issues at
the DSDP debug meeting in Chicago and it was agreed that the platform
should
provide support for it.

Items 7 and 8 rather belong to the Target Management subsystem. The
proposals are posted to the eclipse.dsdp newsgroup.

Item 9. We have similar requests from our customers.

Item 10 - bug #82078

Item 18 - bug #37845

BTW, are you planning to attend the next DSDP meeting in Toronto?

Mikhail
----- Original Message -----
From: "John Cortell" <cortell@xxxxxxxxxxxxxx>
To: "CDT Debug developers list" <cdt-debug-dev@xxxxxxxxxxx>
Sent: Tuesday, June 14, 2005 2:35 PM
Subject: [cdt-debug-dev] CDT debugger features


> Attached is a list and description of core features Freescale requires
> in a
> debugger and therefore deems necessary in Eclipse/CDT, whether this is
> as a
> part of common technology or as a Freescale add-on.  We wish to avoid
> duplication of effort, and as such, would like to solicit feedback from
> the
> community on the various objectives with regard to the following:
>
> - find out if one or more of these features are already on the CDT 3.1
> road-map
> - find out if any individual contributors already have their sights on
> these features--perhaps even have draft or complete implementations not
> yet
> submitted for adoption
> - solicit feedback that will help us develop the features in a way that
> best benefits the community and makes the features more likely to be
> adopted
>
> The items vary in priority and level of difficulty, but they are listed
> in
> no particular order.
>
> John
>
>

_______________________________________________
cdt-debug-dev mailing list
cdt-debug-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cdt-debug-dev