pttrace
Abstract
Sets a trace for the specified packet tree. Packet tree traces consist of statements indicating Kernel Procedures and selected Simulation Kernel actions applied to packets belonging to the specified packet tree.
Syntax
pttrace <pk_tree_id>
| Argument | Type | Description |
|---|---|---|
<pk_tree_id> |
integer | numeric ID of the packet tree-of-interest A packet tree ID can be obtained by using one of several methods: (1) estimating the index of packet tree creation (e.g., “the 50th packet tree”); (2) issuing the ODB command pkmap with a specified packet or with the argument all; (3) issuing the ODB command pkprint with a specified packet; (4) observing a packet tree ID during a previous run of the same simulation. |
Details
A packet tree is a group of packets related to a common ancestor. When a new packet is created by the KPs op_pk_create() or op_pk_create_fmt(), a new packet tree is created as well. However, when a new packet is created by copying an existing packet, either via the KP op_pk_copy() or due to broadcast transmission over a bus or radio link, this new copy packet is part of the same packet tree as the original packet. Each packet tree has a corresponding packet tree ID, which is used to identify the tree to the ODB commands ptmap and pttrace.
Issuing the pttrace command is useful for following the paths of the offspring of a known original packet. Multiple packet tree traces can be active at the same time. A packet tree trace is active from the time it is set until it is suspended or deleted; it is not automatically deleted when all packets in its associated packet tree have been destroyed. Traces specified for packet trees that do not exist are indicated in the output of the status command by the notation “(0 such packets)”.
Example
ODB> pttrace 7
Added trace #2: trace on packets with tree ID (7) (1 such packet)
ODB> status
Breakpoints :
None
Traces :
Full trace is disabled
Encapsulation trace is enabled
Execution trace is disabled
Trace format: indented
2) trace on packets with tree ID (7) (1 such packet)
Actions :
None
Miscellaneous :
Memory tagging is disabled
ODB> cont
...
____________________________ (ODB 18.6.0: Event) ____________________________
* Time : 10.0 sec, [10s]
* Event : execution ID (49), schedule ID (#72), type (remote (start reception))
* Source : execution ID (41), top.pksw2.node_0.xmt [Objid=186] (pt-pt transmitter)
* Data : code (0)
> Module : top.pksw2.hub.rcv3 [Objid=116] (pt-pt receiver)
Kernel Action: Pt-Pt Receiver object
Beginning reception of packet
module (116)
channel (0)
packet ID (7)
...