Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-debug-dev] requesting status on various 3.0 features

John,

Please, see my comments inline.

Mikhail
----- Original Message ----- From: "John Cortell" <r4609c@xxxxxxxxxxxxx>
To: <cdt-debug-dev@xxxxxxxxxxx>
Sent: Friday, June 03, 2005 4:42 PM
Subject: [cdt-debug-dev] requesting status on various 3.0 features


It appears the CDT 3.0 Plan web page hasn't been updated since early
April.
There are a few items on there I was hoping to get an update on; the
items
do not reference a Bugzilla report.

1. Use the call stack limitation feature by Eclipse 3.1.
Not sure what this is. Can someone briefly explain how this feature will

affect CDT debugging?


The number of the stack frames displayed in the Debug view is limited to 100. If the stack depth is greater than 100, only 100 top frames are shown. Currently, this feature is implemented in the CDT. There is an enhancement request to support it in the Eclipse Debug Framework. When implemented, we can remove our implementation and use the generic one. I'm not 100% sure, but it looks like this feature has been deffered.
From the user's point of view it will not affect debugging.

2. Support for user-defined register groups.
What's the status on this?


Work in progress. Planning for M7.

3. Use asynchronous implementation for resume, suspend, step, etc
provided
by Eclipse 3.1.
Not sure what this is. Can someone briefly explain how this feature will

affect CDT debugging?


Similar to the previous one. All these operations must run in the non-UI threads, otherwise the IDE can be blocked. Before it was our responsibility to create a backgroud job to run each of these operations. Now, the Eclipse Debug Platform provides asynchronous implementations, so we had to remove our code.
Will not affect end users.

Finally, is 27892 (display memory as disassembly) going to make it into
3.0? Its status in the report is NEW.


It's very likely that this feature will be deferred.

John

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



Back to the top