Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/Obsolete/MultiCoreDebugWorkingGroup/CompletedFeatures"
Line 12: | Line 12: | ||
This feature has been implemented for CDT 8.0 as part of [https://bugs.eclipse.org/bugs/show_bug.cgi?id=318230 Bug 318230] | This feature has been implemented for CDT 8.0 as part of [https://bugs.eclipse.org/bugs/show_bug.cgi?id=318230 Bug 318230] | ||
+ | |||
+ | == Multi-process debugging == | ||
+ | |||
+ | For targets that don't require the explicit creation of new inferiors, multi-process debugging has been completed since Eclipse 3.5. The work is ongoing for Linux targets in [http://bugs.eclipse.org/237306 Bug 237306]. |
Revision as of 10:37, 23 November 2010
Contents
Multi-core debugging features that have already been implemented
Debugging without the Debug view (Breadcrumb)
As of Eclipse 3.6 (Helios), a debug Breadcrumb has been implemented to dramatically reduce the size of the Debug View. The user can simply manually shrink the Debug View to a single line, and the Breadcrumb will automatically be activated. For details, see user documentation for Debug View and Bug 252677.
Showing cores in Debug view labels
By using the enhancements of GDB 7.1, we can show the core on which each thread runs as an extra part of the Debug View label. We can do the same for processes. The below image shows this.
This feature has been implemented for CDT 8.0 as part of Bug 318230
Multi-process debugging
For targets that don't require the explicit creation of new inferiors, multi-process debugging has been completed since Eclipse 3.5. The work is ongoing for Linux targets in Bug 237306.