prolstop
Abstract
Sets a labeled breakpoint that will stop the simulation when the specified process invokes the KP op_prg_odb_bkpt() with a matching label.
Syntax
prolstop <process_id> [<label>]
| Argument | Type | Description |
|---|---|---|
<process_id> |
integer | numeric process ID of the process-of-interest A process ID can be obtained by issuing the ODB commands objprint or promap, which both display lists of the existing processes associated with a specific module. |
<label> |
string | [optional] one or more space-separated strings specifying which labels in the process to set as breakpoints Each label can include alphanumeric characters, spaces, and selected punctuation, but must be surrounded by double quotes if spaces are included. If no label is given in the command, prolstop displays a list of the labels found in the process model.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
Processors and queues may create multiple processes using the KP op_pro_create() to model subsystems operating within a module. A typical use of this technique is to create multiple instantiations of a single process model. In such cases, a labeled process breakpoint set by the prolstop command can be isolated to a single process instance, proving much more effective than the broader mlstop command.
Labeled process breakpoints are indefinite, because they remain on the pending breakpoint list after being trapped. Breakpoints can be suspended by suspstop, reactivated by actstop, or deleted by delstop.
Example
For this example, the following line of code must be added in the if clause starting on line 4 of the route_pk state enter execs in process model pksw_hub_proc.
op_prg_odb_bkpt ("same_subnet");
----------------------------------------------------------------------------------
ODB> prolstop 5
Following ODB labels are available for the process [5]: same_subnet
ODB> prolstop 5 same_subnet
Added breakpoint #0: stop at label (same_subnet) in process (5)
ODB> status
Breakpoints :
0) stop at label (same_subnet) in process (5)
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 : 5.07578191176 sec, [5s . 75ms 781us 911ns 757ps]
* Event : execution ID (109), schedule ID (#127), type (stream intrpt)
* Source : execution ID (107), top.pksw2.hub.rcv2 (pt-pt receiver)
* Data : instrm (2), packet ID (8)
> Module : top.pksw2.hub.hub [Objid=37] (processor) [process id: 79]
breakpoint #0 trapped : "stop at label (same_subnet) in process (5)"