suspstop
Abstract
Temporarily disables the specified breakpoint, preventing it from being trapped.
Syntax
suspstop <bkpt_id> | all
| Argument | Type | Description |
|---|---|---|
<bkpt_id> |
integer | numeric breakpoint ID of the breakpoint-of-interest A breakpoint ID can be obtained by using the ODB command status, which lists all pending breakpoints in numeric order. |
| all | n/a | Disable all breakpoints. |
Details
When a breakpoint is suspended, ODB will not trap the breakpoint even when its defining conditions are present. The status command lists a suspended breakpoint with the extra text “(suspended)”. A suspended breakpoint can be fully restored to normal condition using the actstop command. All breakpoint types can be suspended by this command, including those set by ODB commands such as evstop, intstop, and mstop.
Example
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> suspstop 1
"stop at time = (100) sec." is disabled.
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> cont
The simulation will execute the breakpoints at t=50 and t=150, skipping over the suspended breakpoint at t=100.