protrace
Abstract
Sets a trace for the specified process. Traces consist of statements indicating process invocation, entry and exit of process states, Kernel Procedure invocation, and selected Simulation Kernel internal actions.
Syntax
protrace <process_id>
| Argument | Type | Description |
|---|---|---|
<process_id> |
integer | numeric process ID of the process-of-interest A process ID can be obtained by using the ODB commands objprint or promap, which both display lists of the existing processes associated with a specific module. |
Details
A process trace issues statements when the specified process is invoked, either by another process or due to a received interrupt. The event that directly or indirectly led to the invocation of a traced process is indicated by an event banner which precedes the trace messages. A process being traced that is invoked by an untraced process might appear to be directly associated with an event because the intervening process isn’t indicated by trace messages. Traces can be suspended by the command susptrace, reactivated by acttrace, or deleted by deltrace.
Example
ODB> protrace 9
Added trace #1: trace on process 9
ODB> cont
_________Invoking process ID (9)_________
+- process ("pksw2_hub_proc_ref")
|
| _________state (init): enter executives_________
|
| +- op_id_self ()
| | object ID (131)
| +-------
|
| +- op_topo_parent (objid)
| | child objid (131)
| | parent objid (8)
| +-------
|
| +- op_topo_parent (objid)
| | child objid (8)
| | parent objid (7)
| +-------
|
| +- op_ima_obj_attr_get_int32 (objid, attr_name, value_ptr)
| | objid (7)
| | attr_name (user id)
| | value (2)
| | completion code (success)
| +-------
|
| _________state (init): exit executives_________
|
| _________transition from state (init) to state (idle)_________
|
| * condition: "default"
|
| _________state (idle): enter executives_________
|
+-------
_________Returning from process ID (9)_________
...