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/BreakpointsWorkingGroup"

< CDT‎ | Obsolete
(Breakpoint Properties Dialog)
Line 1: Line 1:
=== Introduction  ===
+
= Introduction  =
  
 
Purpose of this group is to improve breakpoint features and usability in CDT.
 
Purpose of this group is to improve breakpoint features and usability in CDT.
  
=== Links  ===
+
= Links  =
  
=== Design Notes  ===
+
= Design Notes  =
  
==== Breakpoint Properties Dialog ====
+
== Breakpoint Properties Dialog ==
  
 
The breakpoint properties dialog design directly affects three of the planned bugs:  
 
The breakpoint properties dialog design directly affects three of the planned bugs:  
Line 15: Line 15:
  
 
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.
 
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.
[[Image:BreakpointPropertiesDialog-Overview CDT.png|thumb|left|640px|CDT Breakpoint Properties Dialog - Overview]]
+
[[Image:BreakpointPropertiesDialog-Overview CDT.png|640px|CDT Breakpoint Properties Dialog - Overview]]
  
[[Image:BreakpointPropertiesDialog-Overview WindRiver.png|thumb|left|640px|Wind River Breakpoint Properties Dialog - Overview]]
+
[[Image:BreakpointPropertiesDialog-Overview WindRiver.png|640px|Wind River Breakpoint Properties Dialog - Overview]]
  
  
[[Image:BreakpointPropertiesDialog-Pages CDT.png|thumb|left|640px|CDT Breakpoint Properties Dialog - Pages class hierarchy]]
+
[[Image:BreakpointPropertiesDialog-Pages CDT.png|640px|CDT Breakpoint Properties Dialog - Pages class hierarchy]]
  
[[Image:BreakpointPropertiesDialog-Pages WindRiver.png|thumb|left|640px|Wind River Breakpoint Properties Dialog - Pages class hierarchy]]
+
[[Image:BreakpointPropertiesDialog-Pages WindRiver.png|640px|Wind River Breakpoint Properties Dialog - Pages class hierarchy]]
 +
 
 +
<br>
 +
= Minutes of meetings =
 +
 
 +
== April 19th, 2016 ==
 +
 
 +
=== Attendees ===
 +
 
 +
# Marc Dumais (Ericsson)
 +
# Marc Khouzam (Ericsson)
 +
# Tracy Miranda (Kichwa Coders)
 +
# Jonah Graham (Kichwa Coders)
 +
# Mikhail Khodjaiants (Mentor)
 +
 
 +
 
 +
Hard for users to control where bp are installed on multi-core systems
 +
Bp are affected by multi-session situation
 +
 
 +
Showing target bp under main bp.
 +
    - does not help much for single target
 +
 
 +
Persistence of bp assigned to thread/process/etc is needed

Revision as of 13:06, 19 April 2016

Introduction

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

Links

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. Marc Dumais (Ericsson)
  2. Marc Khouzam (Ericsson)
  3. Tracy Miranda (Kichwa Coders)
  4. Jonah Graham (Kichwa Coders)
  5. Mikhail Khodjaiants (Mentor)


Hard for users to control where bp are installed on multi-core systems Bp are affected by multi-session situation

Showing target bp under main bp.

   - does not help much for single target

Persistence of bp assigned to thread/process/etc is needed

Back to the top