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) |
(→Next Teleconference) |
||
| (192 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 = | |
| − | + | ||
| − | + | Every second Tuesday of the month at 11am Ottawa time <br> | |
| − | + | '''The next one will be on Tuesday May 12th, 2015, 11am<br>''' | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | The call info is the same as for the CDT monthly calls: | |
| − | + | * North America 1-866-569-4992 | |
| + | * Germany 49-692-2224-6059 | ||
| + | * France 33-(0)-17-070-8535 | ||
| + | * UK 0800-033-7806 | ||
| + | * Switzerland 41-44-580-2115 | ||
| + | * Sweden 46-85-063-8386 | ||
| + | * Italy 003-902-3604-8268 | ||
| − | + | Attendees use this: Extension: 700 Passcode: 19455 | |
| − | + | '''Agenda'''<br> | |
| − | + | * Mars release | |
| − | + | * Standalone debugger fails to launch with M6 [http://eclip.se/467109 Bug 467109] | |
| − | + | * RCP Standalone debugger | |
| − | # | + | * Docker contribution |
| − | + | * Register Grouping and Variable Objects for registers | |
| + | * RunControl Grouping | ||
| + | * Memory view fixes | ||
| + | * [https://wiki.eclipse.org/CDT/User/NewIn87#Exited_processes_shown_in_the_debug_view Showing Exited processes] | ||
| + | * Other | ||
| − | = | + | = Previous minutes of meetings = |
| − | [[CDT/MultiCoreDebugWorkingGroup/ | + | : [[CDT/MultiCoreDebugWorkingGroup/calls/minutes | Previous minutes of meetings]] |
| − | = | + | = 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/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/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:43, 12 May 2015
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
Every second Tuesday of the month at 11am Ottawa time
The next one will be on Tuesday May 12th, 2015, 11am
The call info is the same as for the CDT monthly calls:
- North America 1-866-569-4992
- Germany 49-692-2224-6059
- France 33-(0)-17-070-8535
- UK 0800-033-7806
- Switzerland 41-44-580-2115
- Sweden 46-85-063-8386
- Italy 003-902-3604-8268
Attendees use this: Extension: 700 Passcode: 19455
Agenda
- Mars release
- Standalone debugger fails to launch with M6 Bug 467109
- RCP Standalone debugger
- Docker contribution
- Register Grouping and Variable Objects for registers
- RunControl Grouping
- Memory view fixes
- Showing Exited processes
- Other
Previous minutes of meetings
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.