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

CDT/Obsolete/BreakpointsWorkingGroup

< CDT‎ | Obsolete
Revision as of 11:57, 24 May 2016 by Marc.khouzam.gmail.com (Talk | contribs) (Next teleconference)

Introduction

Purpose of this group is to improve breakpoint features and usability in CDT.

Next teleconference

Please see minutes of previous meetings below
The next call will be June 14th, 2016 at 11am (Ottawa time)

  • 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

Design Notes

Breakpoint Properties Dialog

The breakpoint properties dialog design directly affects three of the planned bugs:

  • bug 360291 - Allow user to edit line breakpoint file in properties dialog
  • bug 360295 - Customize property dialog for editing breakpoints
  • bug 360588 - Allow user to edit all its properties prior to creating the breakpoint [DONE]

The data flow in the breakpoint properties dialog is illustrated in the following diagram. Below it is a comparison diagram from the Wind River product. CDT Breakpoint Properties Dialog - Overview

Wind River Breakpoint Properties Dialog - Overview


CDT Breakpoint Properties Dialog - Pages class hierarchy

Wind River Breakpoint Properties Dialog - Pages class hierarchy

Minutes of meetings

April 19th, 2016

Attendees

  1. Mikhail Khodjaiants (Mentor)
  2. Tracy Miranda (Kichwa Coders)
  3. Jonah Graham (Kichwa Coders)
  4. Marc Dumais (Ericsson)
  5. Marc Khouzam (Ericsson)

Minutes

  • Issues
    1. Hard for users to control where breakpoints are installed on multi-core systems
    2. Breakpoints don't work smoothly in a multi-session situation
  • High-level requirements
    1. Users have trouble seeing where a breakpoint actually applies (target, thread, core, etc)
    2. Users need a good way to control where a breakpoint should apply
    3. Need to persist user-configured applicability of breakpoints
    4. Need multiple breakpoints at the same location so as to configure each one differently
    5. Synchronization with the GDB console should work in all cases
  • Can we show columns in the breakpoints view?
  • Actions
    1. Mikhail to re-implement a prototype to show target breakpoint nodes under main platform breakpoint node
    2. Others to provide Mikhail with small list of expectations about what should be shown in the breakpoints view for his prototype
    3. Marc K or Alvaro to prepare demo of Mikhail's patch of usage of Breakpoint view detail pane
    4. Jonah to prepare demo of Mikhail's patch of using colour for breakpoint installation status
    5. Look into how other IDEs handle breakpoints to address such issues:

Back to the top