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)
(Previous minutes of meetings)
(28 intermediate revisions by one other user not shown)
Line 9: Line 9:
 
= Next Teleconference =
 
= Next Teleconference =
  
Every second Tuesday of the month at 11am Ottawa time <br>
+
Jointly with the CDT call.  Please refer to the [[CDT/calls | CDT Call wiki page]]<br>
'''Exceptionally, the next one will be on Tuesday April 14th, 2015, 11am<br>'''
+
  
The call info is the same as for the CDT monthly calls:
+
= Previous minutes of meetings =
  
* North America 1-866-569-4992
+
Minutes up to January 2016 can be found here:
* Germany 49-692-2224-6059
+
[[CDT/MultiCoreDebugWorkingGroup/calls/minutes | Previous minutes of meetings]].
* 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>
+
* 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 =
+
  
: [[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 =
 
= Features of current interest =

Revision as of 10:31, 29 January 2016

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.

  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