Jump to: navigation, search

Difference between revisions of "CDT/MultiCoreDebugWorkingGroup"

< CDT
(Next Teleconference)
(Features of current interest)
(30 intermediate revisions by one other user not shown)
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 August 13th, 2013<br>
+
The next one will be on Tuesday August 12th, 2014<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:
* Ottawa (local call in Ottawa) 1-613-454-1403
+
 
* North America (toll free) 1-877-369-7806
+
* North America 1-866-569-4992
* Germany (local call anywhere in Germany) 49-692-2224-6059
+
* Germany 49-692-2224-6059
* France (local call anywhere in France) 33-17-070-8535
+
* France 33-(0)-17-070-8535
* UK (toll free) 0800-033-7806
+
* 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
 
Attendees use this: Extension: 700 Passcode: 19455
  
 
'''Agenda'''<br>
 
'''Agenda'''<br>
* New CDT proposed schedule
+
* Launch Bar
* Ongoing work
+
* New UI
** Register groups [https://bugs.eclipse.org/235747 Bug 235747]
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=434558 Multi-terminate/Multi-disconnect]
** Multicore Visualizer for all-stop [https://bugs.eclipse.org/409965 Bug 409965]
+
* [https://bugs.eclipse.org/bugs/show_bug.cgi?id=436095 Pin&Clone for Visualizer]
** Dynamic-Printf [https://bugs.eclipse.org/400628 Bug 400628]
+
* Stand-alone debugger
** Trace Control Enhancements [https://bugs.eclipse.org/390827 Bug 390827]
+
* Snapshot feature ''a la'' EDC. Is there interest?
** Show values returned from function calls [https://bugs.eclipse.org/341731 Bug 341731]
+
* Other
** Display of Exited processes [https://bugs.eclipse.org/407340 Bug 407340]
+
  
 
= Previous minutes of meetings =
 
= Previous minutes of meetings =
Line 50: Line 52:
 
# [[CDT/MultiCoreDebugWorkingGroup/GlobalBreakpoints | Global breakpoints]]
 
# [[CDT/MultiCoreDebugWorkingGroup/GlobalBreakpoints | Global breakpoints]]
 
# [[CDT/MultiCoreDebugWorkingGroup/EnhancedBreakpoints | Enhanced Breakpoint Support]]
 
# [[CDT/MultiCoreDebugWorkingGroup/EnhancedBreakpoints | Enhanced Breakpoint Support]]
# [[CDT/MultiCoreDebugWorkingGroup/ExpressionWorkingSets | Expression Working Sets]]
+
# [[CDT/MultiCoreDebugWorkingGroup/NewLaunchUI | New Launch UI]]
  
 
= Features already completed =
 
= Features already completed =

Revision as of 00:59, 10 July 2014

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 August 12th, 2014

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

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