next
Abstract
Advances the simulation until the specified event, then stops at an automatic breakpoint prior to the subsequent event.
Syntax
next
next <num_steps>
next time
| Argument | Type | Description |
|---|---|---|
<num_steps> |
integer | Number of steps to advance |
| time | n/a | Advance to the next time |
Details
The first event executed by this command is the event that was last breakpointed in ODB, and that was described by the last visible event banner. After this and any following events are executed, another banner will appear that describes the subsequent pending event. ODB inserts an initial breakpoint before any simulation events are executed, so if next is the first command issued to ODB, the banner for the first event is printed and the event is breakpointed. Thus, the second invocation of next will actually execute the first event (event #0), as shown in the example.
Labeled breakpoints might be trapped between the issuance of the next command and the automatic breakpoint before the subsequent event: the KP op_prg_odb_bkpt() might be called by a process invoked due to the next command, and match a pending labeled breakpoint. When such situations occur, extra next commands are necessary to proceed beyond the labeled breakpoints to the execution of the subsequent event.
Example
_______________ Simulation Debugger _______________
Type 'help' for Command Summary
ODB> next
__________________________ (ODB 18.6: Event) ____________________________
* Time : 0.0 sec, [0s]
* Event : execution ID (0), schedule ID (#0), type (begin sim intrpt)
* Source : Simulation Kernel
* Data : none
> Module : top.pksw1.hub.hub [Objid=46] (processor)
ODB> n
_________________________ (ODB 18.6: Event) ____________________________
* Time : 0.0 sec, [0s]
* Event : execution ID (1), schedule ID (#1), type (begin sim intrpt)
* Source : Simulation Kernel
* Data : none
> Module : top.pksw1.node_1.src [Objid=63] (processor)