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/MultiCoreDebugWorkingGroup/GlobalBreakpoints"
< CDT | Obsolete | MultiCoreDebugWorkingGroup
(→Global Breakpoints) |
m (Jonah.kichwacoders.com moved page CDT/MultiCoreDebugWorkingGroup/GlobalBreakpoints to CDT/Obsolete/MultiCoreDebugWorkingGroup/GlobalBreakpoints) |
||
| (One intermediate revision by one other user not shown) | |||
| Line 7: | Line 7: | ||
# a combination of the above | # a combination of the above | ||
| − | When a global breakpoint is hit, [[CDT/MultiCoreDebugWorkingGroup/SynchronizedOperations | synchronized run control operations] could automatically be performed, e.g., to stop the entire core. | + | When a global breakpoint is hit, [[CDT/MultiCoreDebugWorkingGroup/SynchronizedOperations | synchronized run control operations]] could automatically be performed, e.g., to stop the entire core. |
Latest revision as of 16:06, 16 January 2020
Global Breakpoints
A global breakpoint is a breakpoint that applies to multiple processes, including processes that are not actively being debugged, or have not yet been created. When a global breakpoint is hit, the debugger will attach automatically to the process that hit the breakpoint. Global breakpoints can be set within:
- a set of existing processes
- all processes already running
- all processes created after this point
- a combination of the above
When a global breakpoint is hit, synchronized run control operations could automatically be performed, e.g., to stop the entire core.