Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "CDT/Obsolete/MultiCoreDebugWorkingGroup"
(→Multi-Core Debugging) |
(→Previous minutes of meetings) |
||
| (215 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
| − | = | + | = Introduction = |
| − | This page documents the activities of CDT's Multi-Core Working Group. This group aims to bring together different people from the community to jointly work on developing multi-core debugging for CDT. The group was first proposed at the CDT Summit 2010 and the suggestion was well received. | + | This page documents the activities of CDT's Multi-Core Working Group. This group aims to bring together different people from the community to jointly work on developing multi-core debugging for CDT. The group was first proposed at the [http://wiki.eclipse.org/CDT/summitfall2010 CDT Summit 2010] and the suggestion was well received. |
| − | + | Although this effort does cover the debugging of target with multiple cores, we use the term ''Multi-core debugging'' in a much wider sense. ''Multi-core debugging'' is meant to describe the simultaneous debugging of multiple cores, processes, threads, or other objects which are represented in standard debugger views. | |
| − | + | Any one interested in helping in this effort is welcome to follow or join the group. Teleconferences are held on a regular basis to discuss progress, issues, features, tasks, etc.<br> | |
| − | + | = Next Teleconference = | |
| − | + | ||
| − | + | Jointly with the CDT call. Please refer to the [[CDT/calls | CDT Call wiki page]]<br> | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | = | + | = Previous minutes of meetings = |
| − | + | Minutes up to January 2016 can be found here: | |
| + | [[CDT/MultiCoreDebugWorkingGroup/calls/minutes | Previous minutes of meetings]]. | ||
| − | + | All future minutes will be documented on the [[CDT/calls | CDT Call wiki page]]. | |
| − | + | = Features of current interest = | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | The following is a list of features have had some effort invested in them but are not ready for release. The effort might have stopped due to lack of resources, but could be easily revived. | |
| − | [[CDT/MultiCoreDebugWorkingGroup/ | + | # [[CDT/MultiCoreDebugWorkingGroup/MultiLevelHierarchy | Multi Level Hierarchy in the Debug View]] |
| + | # [[CDT/MultiCoreDebugWorkingGroup/DebugElementsGrouping | Grouping of debug view elements]] | ||
| + | # [[CDT/MultiCoreDebugWorkingGroup/DebugElementsHiding | Hiding of debug view elements]] | ||
| + | # [[CDT/MultiCoreDebugWorkingGroup/DebugViewLayouts | User-selectable Debug View layouts]] | ||
| + | # [[CDT/MultiCoreDebugWorkingGroup/VisualizerView | Visualizer View]] | ||
| + | #* A first version of the Multicore Visualizer as well as the Visualizer Framework are part of the Juno release | ||
| + | #* Many enhancements are still of interest. | ||
| + | # [[CDT/MultiCoreDebugWorkingGroup/SynchronizedOperations | Synchronized/Grouped Run Control Operations]] | ||
| + | #* User defines a group (cores or processes or threads) which makes up the application, and can perform application-level operations on it | ||
| + | # [[CDT/MultiCoreDebugWorkingGroup/GlobalBreakpoints | Global breakpoints]] | ||
| + | # [[CDT/MultiCoreDebugWorkingGroup/EnhancedBreakpoints | Enhanced Breakpoint Support]] | ||
| + | # [[CDT/MultiCoreDebugWorkingGroup/NewLaunchUI | New Launch UI]] | ||
| − | = | + | = Features already completed = |
| − | [[CDT/MultiCoreDebugWorkingGroup/ | + | [[CDT/MultiCoreDebugWorkingGroup/CompletedFeatures | List of features that have already been implemented.]] |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | = Potential future features = | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | [[CDT/MultiCoreDebugWorkingGroup/PotentialFeatures | List of features that have been proposed]] and may be addressed in the future. | |
| − | + | ||
| − | = | + | = Use Cases = |
| − | [ | + | * [[CDT/MultiCoreDebugWorkingGroup/UseCaseKernelDebug | Kernel Debug (also: bare-metal/bootloader debug)]] |
| − | [ | + | * [[CDT/MultiCoreDebugWorkingGroup/UseCaseEmbeddedApplicationDebug | Embedded Application Debug]] |
| + | ** [[CDT/MultiCoreDebugWorkingGroup/UseCaseApplicationDebug | Develop-on-Target (local application debug)]] | ||
Revision as of 10:31, 29 January 2016
Contents
Introduction
This page documents the activities of CDT's Multi-Core Working Group. This group aims to bring together different people from the community to jointly work on developing multi-core debugging for CDT. The group was first proposed at the CDT Summit 2010 and the suggestion was well received.
Although this effort does cover the debugging of target with multiple cores, we use the term Multi-core debugging in a much wider sense. Multi-core debugging is meant to describe the simultaneous debugging of multiple cores, processes, threads, or other objects which are represented in standard debugger views.
Any one interested in helping in this effort is welcome to follow or join the group. Teleconferences are held on a regular basis to discuss progress, issues, features, tasks, etc.
Next Teleconference
Jointly with the CDT call. Please refer to the CDT Call wiki page
Previous minutes of meetings
Minutes up to January 2016 can be found here: Previous minutes of meetings.
All future minutes will be documented on the CDT Call wiki page.
Features of current interest
The following is a list of features have had some effort invested in them but are not ready for release. The effort might have stopped due to lack of resources, but could be easily revived.
- Multi Level Hierarchy in the Debug View
- Grouping of debug view elements
- Hiding of debug view elements
- User-selectable Debug View layouts
- Visualizer View
- A first version of the Multicore Visualizer as well as the Visualizer Framework are part of the Juno release
- Many enhancements are still of interest.
- Synchronized/Grouped Run Control Operations
- User defines a group (cores or processes or threads) which makes up the application, and can perform application-level operations on it
- Global breakpoints
- Enhanced Breakpoint Support
- New Launch UI
Features already completed
List of features that have already been implemented.
Potential future features
List of features that have been proposed and may be addressed in the future.