Jump to: navigation, search

Difference between revisions of "CDT/MultiCoreDebugWorkingGroup"

< CDT
(Next Teleconference)
(Next Teleconference)
Line 10: Line 10:
  
 
Every second Tuesday of the month at 11 a.m. Ottawa time <br>
 
Every second Tuesday of the month at 11 a.m. Ottawa time <br>
The next one will be on Tuesday March 12th, 2013<br>
+
The next one will be on Tuesday April 9th, 2013<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 22: Line 22:
  
 
'''Agenda'''<br>
 
'''Agenda'''<br>
* Kepler release
+
* Status of Kepler features
* Pin&Clone in platform [https://bugs.eclipse.org/145635 Bug 145635]
+
* Expression working sets vs Expression Groups [https://bugs.eclipse.org/372181 372181]
* Assembly view vs Disassembly view
+
* CPU usage shown in Multicore Visualizer [https://bugs.eclipse.org/396268 Bug 396268]
+
* Expression working sets [https://bugs.eclipse.org/372181 372181]
+
 
* Step into Selection [https://bugs.eclipse.org/244865 Bug 244865]  
 
* Step into Selection [https://bugs.eclipse.org/244865 Bug 244865]  
 
* Dynamic-printf [https://bugs.eclipse.org/400628 Bug 400628]
 
* Dynamic-printf [https://bugs.eclipse.org/400628 Bug 400628]
 +
* Multicore Visualizer filtering
 
* Hardware breakpoints [https://bugs.eclipse.org/332993 Bug 332993]
 
* Hardware breakpoints [https://bugs.eclipse.org/332993 Bug 332993]
* Visualizer features
 
  
 
= Previous minutes of meetings =
 
= Previous minutes of meetings =

Revision as of 15:58, 12 March 2013

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 11 a.m. Ottawa time
The next one will be on Tuesday April 9th, 2013

The call info is the same as for the CDT monthly calls:

  • Ottawa (local call in Ottawa) 1-613-454-1403
  • North America (toll free) 1-877-369-7806
  • Germany (local call anywhere in Germany) 49-692-2224-6059
  • France (local call anywhere in France) 33-17-070-8535
  • UK (toll free) 0800-033-7806

Attendees use this: Extension: 700 Passcode: 19455

Agenda

  • Status of Kepler features
  • Expression working sets vs Expression Groups 372181
  • Step into Selection Bug 244865
  • Dynamic-printf Bug 400628
  • Multicore Visualizer filtering
  • Hardware breakpoints Bug 332993

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. Expression Working Sets

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