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)
Line 23: Line 23:
 
'''Agenda'''<br>
 
'''Agenda'''<br>
 
* Support for GDB breakpoint notifications [https://bugs.eclipse.org/392512 Bug 392512]
 
* Support for GDB breakpoint notifications [https://bugs.eclipse.org/392512 Bug 392512]
* Enhanced expressions for both variables and registers [https://bugs.eclipse.org/394408 Bug 394408]
+
* Reverse debugging breakpoint action [https://bugs.eclipse.org/365776 Bug 365776]
* Reverse debugging breakpoint action
+
* Pin&Clone in platform [https://bugs.eclipse.org/145635 Bug 145635]
 +
* Extend CDT launch to allow external profiling [https://bugs.eclipse.org/391608 Bug 391608]
 
* CPU usage shown in Multicore Visualizer
 
* CPU usage shown in Multicore Visualizer
* Pin&Clone in platform
+
* Expression working sets [https://bugs.eclipse.org/372181 372181]
* Expression working sets [https://bugs.eclipse.org/372181 Bug 372181]
+
* Enhanced expressions for both variables and registers [https://bugs.eclipse.org/394408 Bug 394408]
* Generic Launch shortcuts
+
  
 
= Previous minutes of meetings =
 
= Previous minutes of meetings =

Revision as of 16:16, 7 December 2012

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 December 11th, 2012

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

  • Support for GDB breakpoint notifications Bug 392512
  • Reverse debugging breakpoint action Bug 365776
  • Pin&Clone in platform Bug 145635
  • Extend CDT launch to allow external profiling Bug 391608
  • CPU usage shown in Multicore Visualizer
  • Expression working sets 372181
  • Enhanced expressions for both variables and registers Bug 394408

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

Copyright © Eclipse Foundation, Inc. All Rights Reserved.