cont
Abstract
Continues the execution of the simulation from the current breakpoint, until another breakpoint is encountered, the simulation terminates, or the user types <control>-c.
Syntax
cont
| Argument | Type | Description |
|---|---|---|
| no arguments |
Details
Breakpoints or traces that have been set in previous ODB commands will affect the simulation as it continues execution: existing breakpoints will halt the simulation when encountered, and existing traces will print information or execute user-defined statements. If no breakpoints are set and <control>-c is not used, the simulation proceeds to its normal conclusion.
Example
ODB> tstop 25
Added breakpoint #1: stop at time = (25) sec.
ODB> status
Breakpoints :
1) stop at time = (25) 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 : 25.0 sec, [25s]
* Event : execution ID (129), schedule ID (#126), type (self intrpt)
* Source : execution ID (121), top.pksw1.node_0.src [Objid=11] (processor)
* Data : code (1)
> Module : top.pksw1.node_0.src [Objid=11] (processor) [process id: 0]
breakpoint #1 trapped : "stop at time = (25) sec."