Re: [cdt-debug-dev] address spaces

["Alain Magloire" <alain@xxxxxxx>]

Bonjour,
   I've been having email problems, lately.
> 
> Oh, we certainly wouldn't expect something like this to be addressed in 
> 3.0. My understanding is this mailing list is for discussing, among other 
> things, the future direction of the CDT debug technology. Much of what I'll 
> be posting to this list regards Freescale requirements and intentions that 
> we hope to materialize over then next 3 - 12 months.
> 

Yes, you are bringing some very interesting aspects here.
Now we are not sure on how to integrate this, in term of UI 
how to make this intuitive and easy for the user.
In the CDT core debug framework to provide this functionnality.

Agree, we should tackle the problem for the next version and
I'll be curious to see your previous solutions in term of UI and how
we can make this work within the Eclipse/CDT framework.
So far we been looking at variable in terms of Stackframe(local),
thread(TLS) and Process(globals).  Maybe having a different context
on how to retrieve variable should be explore.

PS:  to clear things a little, if you are planning to look a the CDT debug
code, we have 2 APIs + the Platform Debug API(PDI)

(1) the PDI is based on IDebugElement hierarchy and provided by the platform
(2) CDT extends the IDebugElement and provide its own extension
	see org.eclipse.cdt.deug.core.model
(3) The CDI which serves as layer to isolate cdt between the possible
    different backends(for example different GDB).


PS2: For your question concerning the resume of the Chicago meeting ... lost my emails
   but I believe it was posted on the newsgroup of the DSP.