susptrace
Abstract
Temporarily disables the specified trace, preventing it from generating trace messages or enabling user-defined trace statements.
Syntax
susptrace <trace_id> | all
| Argument | Type | Description |
|---|---|---|
<trace_id> |
integer | numeric trace ID of the trace-of-interest A trace ID can be obtained by using the ODB command status, which lists all pending traces in numeric order. |
| all | n/a | Disable all traces. |
Details
When a trace is suspended, ODB will not issue trace messages even when its defining conditions are present. The status command lists a suspended trace with the extra text “(suspended)”. A suspended trace can be fully restored to normal condition using the acttrace command. All trace types can be suspended by this command, including those set by ODB trace commands such as fulltrace, mtrace, and pktrace. Suspending traces is useful during temporary simulation intervals where trace information is not of interest.
Example
ODB> status
Breakpoints :
None
Traces :
Full trace is disabled
Encapsulation trace is enabled
Execution trace is disabled
Trace format: indented
0) trace on packet with ID (45) (packet in system)
1) trace on packets with tree ID (46) (1 such packets)
2) trace on module (top.pksw1.node_0.xmt)
Actions :
None
Miscellaneous :
Memory tagging is disabled
ODB> susptrace 2
"trace on module (top.pksw1.node_0.xmt)" is disabled.
ODB> status
Breakpoints :
None
Traces :
Full trace is disabled
Encapsulation trace is enabled
Execution trace is disabled
Trace format: indented
0) trace on packet with ID (45) (packet in system)
1) trace on packets with tree ID (46) (1 such packets)
2) trace on module (top.pksw1.node_0.xmt) (suspended)
Actions :
None
Miscellaneous :
Memory tagging is disabled