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/Archive/Debug/Catchpoints support"
m (→Workflow & UI) |
m (→Catchpoint contributions) |
||
| Line 13: | Line 13: | ||
== Catchpoint contributions == | == Catchpoint contributions == | ||
| − | * Main | + | * Main Catchpoints attributes would consist of Catchpoint type (event type - String) and Extra argument (Object) |
* Plugin can contribute via extension points of programmatically: | * Plugin can contribute via extension points of programmatically: | ||
** new catchpoint type, and whether it will use extra argument or not. Label for this catchpoint type and Label for the argument. | ** new catchpoint type, and whether it will use extra argument or not. Label for this catchpoint type and Label for the argument. | ||
| − | ** for advanced editing of argument(s) plugin can contribute class that implements Control (To view/edit extra argument) and implement some interface to get/set extra argument | + | ** for advanced editing of argument(s) plugin can contribute class that implements Control (To view/edit extra argument) and implement some interface to get/set extra argument |
== Implementation == | == Implementation == | ||
* CBreakpoint already provides extensibility mechanism that can be used for catchpoint contributions? | * CBreakpoint already provides extensibility mechanism that can be used for catchpoint contributions? | ||
* To represent event type there is two options: use marker type or use marker attribute | * To represent event type there is two options: use marker type or use marker attribute | ||
Revision as of 16:30, 8 April 2008
This document describe design ideas of adding catchpoints support to CDT
Workflow & UI
- Adding catchpoint
- From breakpoints view, right click Add catchpoint... Dialog opens. Dialog contains type of event to catch and maybe additional argument field.
- From console, triggers adding breakpoints by backend
- Removing catchpoint
- Removing catchpoint from breakpoints view, select breakpoint, right click -> Delete
- From console, triggers deleting breakpoint by backend
- Viewing/Editing
- Select catchpoint in breakpoints view, right click -> Show breakpoint properties
- Catchpoint properties contain common page, conditions and triggered actions.
Catchpoint contributions
- Main Catchpoints attributes would consist of Catchpoint type (event type - String) and Extra argument (Object)
- Plugin can contribute via extension points of programmatically:
- new catchpoint type, and whether it will use extra argument or not. Label for this catchpoint type and Label for the argument.
- for advanced editing of argument(s) plugin can contribute class that implements Control (To view/edit extra argument) and implement some interface to get/set extra argument
Implementation
- CBreakpoint already provides extensibility mechanism that can be used for catchpoint contributions?
- To represent event type there is two options: use marker type or use marker attribute