Re: [cdt-debug-dev] Need feedback for support of multiple address spaces

[Mattias Bertilsson <matb@xxxxxxx>]

Here is my two cents, take it or leave it...

Both as a CDT user and as a plugin developer I like Adam's suggestion better. I think address space id:s and address values are two different things. For instance, I think the user will change addresses much more often than he will change address space id:s.

Why define a special syntax just to be able to put them in the same text field?

If we want some more intuitive way to select address space, isn't that a reason in itself to keep the address space id out of the address text field?

/Mattias Bertilsson


Adam Finucane wrote:

Comments inline...

On Friday 28 October 2005 09:59, John Cortell wrote:
  

Comments inline...

At 04:43 PM 10/27/2005, Adam Finucane wrote:
    

We use the "<space>:<address>" syntax to specify the starting address of
the memory space monitor. The problem with this syntax is there is no way
to know what the magical word for "space" is. There is no indication in
the user interface as to what the space could possible be, or even if
there is more than one memory space available to view.

I think that a combo box could be used to specify a list of memory spaces
available for selection to the user. The list memory space names that are
available can be provided by the Target. If there is only one memory space
the combo can just not be added.
      

My thoughts there is that there would be a (DSDP) view that would let the
user see a list of available address spaces for the debug session. The
debugger back-end might populate that, perhaps with info from the binary
parser, or from the target. My point here is that I don't think cluttering
the memory window with a new control is worth while. There may be other
views where the user might find himself asking "What are the available
spaces?". Having a central location for that info seems best to me.
    

I think we both agree that a list of available memory spaces needs to be 
provided to the user. We are in a disagreement about how they are presented 
and how the user should enter the memory spaces when it is required. Could I 
suggest that you allow the UI to be customizable enough, from a developers 
point of view, so a preferred solution can be implemented by third parties.

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

begin:vcard
fn:Mattias Bertilsson
n:Bertilsson;Mattias
org:ENEA Embedded Technology AB;Research & Development 
adr:SE-164 21 KISTA;;Box 1033;;;;Sweden
email;internet:matb@xxxxxxx
title:Senior Software Engineer
tel;work:+46 8 507 140 00
version:2.1
end:vcard