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.
Difference between revisions of "CDT/Obsolete/BreakpointsWorkingGroup"
(→April 19th, 2016) |
|||
| Line 37: | Line 37: | ||
# Mikhail Khodjaiants (Mentor) | # Mikhail Khodjaiants (Mentor) | ||
| + | === Minutes === | ||
| − | Hard for users to control where | + | * Issues |
| − | + | *# Hard for users to control where breakpoints are installed on multi-core systems | |
| − | + | *# Breakpoints don't work smoothly in a multi-session situation | |
| − | + | * High-level requirements | |
| − | + | *# Users have trouble seeing where a breakpoint actually applies (target, thread, core, etc) | |
| − | + | *# Users need a good way to control where a breakpoint should apply | |
| − | + | *# Need to persist user-configured applicability of breakpoints | |
| + | *# Need multiple breakpoints at the same location so as to configure each one differently | ||
| + | *# Synchronization with the GDB console should work in all cases | ||
Revision as of 13:11, 19 April 2016
Contents
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.
Minutes of meetings
April 19th, 2016
Attendees
- Marc Dumais (Ericsson)
- Marc Khouzam (Ericsson)
- Tracy Miranda (Kichwa Coders)
- Jonah Graham (Kichwa Coders)
- Mikhail Khodjaiants (Mentor)
Minutes
- Issues
- Hard for users to control where breakpoints are installed on multi-core systems
- Breakpoints don't work smoothly in a multi-session situation
- High-level requirements
- Users have trouble seeing where a breakpoint actually applies (target, thread, core, etc)
- Users need a good way to control where a breakpoint should apply
- Need to persist user-configured applicability of breakpoints
- Need multiple breakpoints at the same location so as to configure each one differently
- Synchronization with the GDB console should work in all cases