lstop
Abstract
Sets a labeled breakpoint. The breakpoint will stop the simulation when the KP op_prg_odb_bkpt() is invoked with a matching label.
Syntax
lstop <label>
| Argument | Type | Description |
|---|---|---|
<label> |
string | label string of the breakpoint The label can include alphanumeric characters, spaces, and selected punctuation, but must be surrounded by double quotes if spaces are included. The labels used for breakpoints exist in a different space from those used by labeled traces. Traces and breakpoints can have labels with the same name, but they do not affect each other. |
Details
A labeled breakpoint is trapped when the KP op_prg_odb_bkpt() is invoked with a label argument that matches the breakpoint label. Labeled breakpoints are indefinite because they are associated with a repeatable situation, and they remain on the pending breakpoint list after being trapped. Breakpoints can be suspended by suspstop, reactivated by actstop, or deleted by delstop.
Example
This example assumes that a statement similar to the following one appears in the code to conditionally set the breakpoint label.
if (dest_subnet == 2)
op_prg_odb_bkpt ("subnet = 2");
----------------------------------------------------------------------------------
ODB> lstop "subnet = 2"
Added breakpoint #0: “stop at label = (subnet = 2)”
ODB> status
Breakpoints :
0 stop at label = (subnet = 2)
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 : 3.50558963718 sec, [3s . 505ms 589us 637ns 176ps]
* Event : execution ID (157), schedule ID (#179), type (stream intrpt)
* Source : execution ID (156), top.pksw1.hub.rcv2 (pt-pt receiver)
* Data : instrm (2), packet ID (14)
> Module : top.pksw1.hub.hub [Objid=15] (processor) [process id: 50]
breakpoint #0 trapped : "stop at label (subnet = 2)"