actstop
Abstract
Reactivates a breakpoint that was previously suspended by the ODB command suspstop.
Syntax
actstop <bkpt_id> | all
| Argument | Type | Description |
|---|---|---|
<bkpt_id> |
integer | numeric breakpoint ID of the breakpoint-of-interest A breakpoint ID for this argument can be obtained by using the ODB command status, which lists all pending breakpoints in numeric order. |
| all | n/a | Reactivate all suspended breakpoints. |
Details
Reactivation of a breakpoint cancels out the effect of suspension, enabling the breakpoint to be trapped when its conditions are matched. If a suspended time breakpoint (defined by the tstop command) is reactivated after its specified time value has passed, it will remain on the pending breakpoint list, and will be trapped after the next cont command is issued. The example below assumes that time breakpoints have already been defined for 50 and 100 seconds, and the breakpoint at 100 seconds has been suspended.
Example
ODB> status
Breakpoints :
0) stop at time = (50) sec.
1) stop at time = (100) sec. (suspended)
2) stop at time = (150) sec.
Traces :
Full trace is disabled
Encapsulation trace is enabled
Execution trace is disabled
Trace format: indented
No other traces
Actions :
None
Miscellaneous :
Memory tagging is disabled
ODB> actstop 1
"stop at time = (100) sec." is reenabled.
ODB> status
Breakpoints :
0) stop at time = (50) sec.
1) stop at time = (100) sec.
2) stop at time = (150) sec.
Traces :
Full trace is disabled
Encapsulation trace is enabled
Execution trace is disabled
Trace format: indented
No other traces
Actions :
None
Miscellaneous :
Memory tagging is disabled
ODB> cont
____________________________ (ODB 18.6.0: Event) ____________________________
* Time : 50.0 sec, [50s]
* Event : execution ID (329), schedule ID (#326), type (self intrpt)
* Source : execution ID (321), top.pksw1.node_0.src [Objid=11] (processor)
* Data : code (1)
> Module : top.pksw1.node_0.src [Objid=11] (processor) [process id: 0]
breakpoint #0 trapped : "stop at time = (50) sec."