Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 106205

Summary: [plan item] Enhance the debug platform
Product: [Eclipse Project] Platform Reporter: Mike Wilson <Mike_Wilson>
Component: DebugAssignee: Platform-Debug-Inbox <platform-debug-inbox>
Status: VERIFIED FIXED QA Contact:
Severity: enhancement    
Priority: P4 CC: ciukes, cocoakevin, eclipse, ed.burnette, gunnar, hampus, mark.melvin, martin.gutschelhofer, mimrisek, mlists, recoskie, thomasf
Version: 3.1Keywords: plan
Target Milestone: 3.2 M6   
Hardware: All   
OS: All   
Whiteboard:

Description Mike Wilson CLA 2005-08-05 12:40:57 EDT
The debug support in Eclipse is increasingly being used in areas that require more flexible mechanisms 
than those required by simple Java programs. Potential work areas include: the integration of flow control, 
async/cancellation into debug APIs; update policies in debug views (i.e. ensure view updates before 
proceeding vs. let debugger go as fast as it can and let the views catch up); a flexible debug model 
element hierarchy to account for different architectures such as multi-core processors, thousands of 
threads, etc; and introduction of table trees in standard debug views for better/flexible presentation. 
[Debug]
Comment 1 Darin Wright CLA 2005-08-05 16:06:01 EDT
Link to proposal on flexible hierarchy:

http://dev.eclipse.org/viewcvs/index.cgi/*checkout*/platform-debug-
home/r3_2/docs/flexible_hierarchy.html?rev=HEAD&content-type=text/html
Comment 2 Mike Wilson CLA 2006-02-14 15:10:33 EST
The text of this item in the plan has changed. The new text is:
"
The debug support in Eclipse is increasingly being used in areas that require more flexible mechanisms than those required by simple Java programs. Features will be provided as provisional API subject to change in a future release. Features include: a flexible element hierarchy in debug views to account for different architectures such as multi-core processors, thousands of threads, etc; asynchronous, cancellable interactions when retrieving view content and labels; model driven view updates; a debug context service allowing for retargettable debug actions, flexible view wiring and pluggable source lookup. [Debug]
"
See also bug 127874, for further debug work.
Comment 3 Darin Wright CLA 2006-03-13 16:53:09 EST
Marking fixed. During 3.2, provisional support has been added for the following:

* Flexible element hierarchy in all debug views (except breakpoint view) with asynchronous content retrieval - @see IAsynchronousContentAdapter
* Asynchronous label generation - @see IAsynchronousLabelAdapter
* Support for columns and cell editors in 'single model' views - @see IColumnPresentationFactoryAdapter and IColumnEditorFactoryAdapter
* Model driven view updates - @see IModelProxyFactoryAdapter
* Asynchronous, retargettable debug actions - @see IAsynchronousTerminateAdapter, IAsynchronousStepAdapter, etc.
* Debug context service - @see IDebugContextManager, IDebugContextProvider, IDebugContextListener
* Flexible view wiring - the variables view sets its input to be the active debug context rather than being hard-wired to the selection in the debug view 

New bug reports should be opened as neccessary to deal with related issues/bugs. 
Comment 4 Darin Wright CLA 2006-03-29 16:03:31 EST
Marking Verified.