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)
(24 intermediate revisions by 2 users not shown)
Line 9: Line 9:
 
= Next Teleconference =
 
= Next Teleconference =
  
Every second Tuesday of the month at 11 a.m. Ottawa time <br>
+
Every second Tuesday of the month at 11am Ottawa time <br>
The next one will be on Tuesday May 13th, 2014<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:
 
The call info is the same as for the CDT monthly calls:
Line 25: Line 25:
  
 
'''Agenda'''<br>
 
'''Agenda'''<br>
* Luna release after feature freeze
+
* Grouping feature
** Testing
+
* VarObj registers
** Any issues?
+
* Memory view fixes
* [[CDT/User/NewIn84#Dynamic-printf | Dynamic Printf]]
+
* Other
  
 
= Previous minutes of meetings =
 
= Previous minutes of meetings =
Line 49: Line 49:
 
# [[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 =

Revision as of 12:37, 17 March 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
Exceptionally, the next one will be on Tuesday April 14th, 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

  • Grouping feature
  • VarObj registers
  • Memory view fixes
  • 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