From:
cdt-debug-dev-bounces@xxxxxxxxxxx [mailto:cdt-debug-dev-bounces@xxxxxxxxxxx] On Behalf Of John Cortell
Sent: Friday, October 28, 2005
4:15 PM
To: CDT Debug developers list
Subject: Re: [cdt-debug-dev] Need
feedback for support ofmultipleaddress spaces in Memory View
It seems to me there will be various places where a space+address
syntax will need to be displayed and accepted as a single string entity.
Consider a variable view; I can conceivably have two pointer variables
displayed in a view, each pointing to a location in a distinct address space.
Also consider the scenario of adding the following item to an _expression_ view
(char
*)(0x042810 + 32)
In a debug session targeting a multi address-space environment, one would want/need
to enter something like
(char*)(n:0x042810
+ 32)
So, I don't see how we could avoid having an address string representation that
includes the address space.
It seems to me having the same interaction in the memory window would prove
more consistent with the rest of the debugger.
John
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
