prodiag
Abstract
Executes the diagnostic block of the specified process.
Syntax
prodiag <process_id>
| 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. |
Details
The diagnostic block of a process model is an editing pad that can contain multiple C statements, for diagnostic purposes within the context of ODB (a full description of diagnostic blocks appears in “Using Diagnostic Blocks in ODB” on page 53). Diagnostic statements have access to process state variables, and can thus be used to display their values. The prodiag command executes the whole diagnostic block; the alternative command proldiag can be used to execute a subset of the diagnostic block.
Example
For this example, the following code must be added to the indicated portions of the pksw_nd_proc process model:
diagnostic block: printf ("\n(%d packets transmitted)\n", xmit_packets);
xmt state enter execs: xmit_packets++;
init state enter execs: xmit_packets = 0;
state variables: int \xmit_packets;
----------------------------------------------------------------------------------
...
breakpoint #0 trapped : "stop at time (50) sec."
ODB> objmap pksw1.node0.proc
Obj ID Obj Name Obj Type Parent ID
-----------------------------------------------------------------------
43 top.pksw1.node0.proc processor 3
ODB> promap 43
________________________________________________________________
Active Processes for Module (23)
process ID process model process tag
---------- ------------- -----------
1 pksw_nd_proc (none)
ODB> prodiag 1
(34 packets transmitted)