Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "CDT/Obsolete/MultiCoreDebugWorkingGroup"

< CDT‎ | Obsolete
(Next Teleconference)
(Next Teleconference)
(130 intermediate revisions by 4 users not shown)
Line 3: Line 3:
 
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.
 
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 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.
+
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. Teleconference are held on a regular basis to discuss progress, issues, features, tasks, etc.<br>
+
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>
Currently, we have conference calls every two weeks.
+
  
 
= Next Teleconference =
 
= Next Teleconference =
  
Tuesday March 8th, 2011 at 11 a.m. Ottawa time <br>
+
Every second Tuesday of the month at 11am Ottawa time <br>
Canada and US Toll Free: 1 877 748-5444, [[CDT/MultiCoreDebugWorkingGroup/calls | International Numbers]]<br>
+
'''The next one will be on Tuesday May 12th, 2015, 11am<br>'''
Conference ID: 691 8070#<br>
+
WebEx session:<br>
+
Or directly at http://ti.webex.com and entering the meeting number <br>
+
  
'''Agenda'''
+
The call info is the same as for the CDT monthly calls:
* API freeze
+
 
** Does it affect provisional/internal/experimental APIs?
+
* North America 1-866-569-4992
** What do we have time for?
+
* Germany 49-692-2224-6059
* Global action set for "C/C++ Advanced Debugging"?
+
* France 33-(0)-17-070-8535
* EclipseCon multicore debug workshop
+
* UK 0800-033-7806
* Visualizer view
+
* Switzerland 41-44-580-2115
** Automated build
+
* Sweden 46-85-063-8386
* Grouping
+
* Italy 003-902-3604-8268
* Multi-process
+
 
** Adding a way to create a new process from the Attach dialog
+
Attendees use this: Extension: 700 Passcode: 19455
** About to commit hiding of the inferior
+
 
* Synchronized operations
+
'''Agenda'''<br>
* Enhanced Breakpoint Support
+
* Register Grouping and Variable Objects for registers
 +
* Migrate Run Launch to DSF
 +
* RunControl Grouping
 +
* Memory view fixes
 +
* Showing Exited processes
 
* Other
 
* Other
<br>
 
  
 
= Previous minutes of meetings =
 
= Previous minutes of meetings =
Line 39: Line 38:
 
= Features of current interest =
 
= Features of current interest =
  
The following is a list of features that are actively being worked on.
+
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/MultiLevelHierarchy | Multi Level Hierarchy in the Debug View]]
Line 46: Line 45:
 
# [[CDT/MultiCoreDebugWorkingGroup/DebugViewLayouts | User-selectable Debug View layouts]]
 
# [[CDT/MultiCoreDebugWorkingGroup/DebugViewLayouts | User-selectable Debug View layouts]]
 
# [[CDT/MultiCoreDebugWorkingGroup/VisualizerView | Visualizer View]]
 
# [[CDT/MultiCoreDebugWorkingGroup/VisualizerView | Visualizer View]]
# [[CDT/MultiCoreDebugWorkingGroup/OSAwareness | OS-awareness]]
+
#* 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]]
 
# [[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
 
#* User defines a group (cores or processes or threads) which makes up the application, and can perform application-level operations on it
# [[CDT/MultiCoreDebugWorkingGroup/MultiProcess | Multi-Process debugging]]
 
 
# [[CDT/MultiCoreDebugWorkingGroup/GlobalBreakpoints | Global breakpoints]]
 
# [[CDT/MultiCoreDebugWorkingGroup/GlobalBreakpoints | Global breakpoints]]
 
# [[CDT/MultiCoreDebugWorkingGroup/EnhancedBreakpoints | Enhanced Breakpoint Support]]
 
# [[CDT/MultiCoreDebugWorkingGroup/EnhancedBreakpoints | Enhanced Breakpoint Support]]
 +
# [[CDT/MultiCoreDebugWorkingGroup/NewLaunchUI | New Launch UI]]
  
 
= Features already completed =
 
= Features already completed =
Line 60: Line 60:
  
 
[[CDT/MultiCoreDebugWorkingGroup/PotentialFeatures | List of features that have been proposed]] and may be addressed in the future.
 
[[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 12:29, 14 April 2015

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

  • Register Grouping and Variable Objects for registers
  • Migrate Run Launch to DSF
  • RunControl Grouping
  • Memory view fixes
  • Showing Exited processes
  • Other

Previous minutes of meetings

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.

  1. Multi Level Hierarchy in the Debug View
  2. Grouping of debug view elements
  3. Hiding of debug view elements
  4. User-selectable Debug View layouts
  5. 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.
  6. 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
  7. Global breakpoints
  8. Enhanced Breakpoint Support
  9. 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.

Use Cases

Back to the top