Re: [cdt-debug-dev] address spaces

["Alain Magloire" <alain@xxxxxxx>]

> And of course, the UI tweaks involves not only displayed addresses, but
> the formatting of addresses entered by the user. For example, the Memory
> Window would need to accept an address in the form shown above.<br><br>
> This specialized behavior would be exposed only in debug sessions that
> target hardware that needs it. The debugger would query that need from
> the back end (debugger plugin).<br><br>
> Martin, I'm eager to hear what your requirements are and whether the
> support described here would meet them.<br><br>
> Alain, does all of this seem reasonable from the perspective of the code
> and API hit to the CDT/CDI layers (again, down the road, not
> now).<br><br>

[...]
[.. good discussion deleted ...]

Sorry for the delay,
  Yes, it does look like a viable solution, at least something
that we should explore for the next version.
Can you make a proposition on how or rather what kind of interface
that an IAddress object should have to meet you requirements.
There will probably be some changes in the Core/UI to make sure
we do treat addresses not like a simple string/long but rather as
an opaque object with certain attributes.

If the experience is succesfull and if there is a need we should probably move this
or at least make pressure to move the concept down to the platform

Note: The CDI API is a way to isolate the CDT debugger from the
backends but in the future it should not be the only way of integration.
There are some drawbacks.