tstop

Abstract

Sets a breakpoint for the specified time. The breakpoint will stop the simulation at the first event with a scheduled time greater than or equal to the specified time.

Syntax

tstop [<abs_time> | +<rel_time>]

Argument Type Description
<abs_time> double absolute simulation time for the breakpoint
<rel_time> double relative simulation time for the breakpoint

Details

A time breakpoint is trapped when an event that was scheduled for a time greater than or equal to the specified time is removed from the event list immediately prior to it execution.

Note: If the simulation is using quantum time values, the tstop time argument is converted into a multiple of the quantum value. This ensures that the break will occur at the first event in the corresponding time quantum.

Time breakpoints are “single-shot”, because they are associated with a non-repeatable time value and are removed from the pending breakpoint list after being trapped. Breakpoints can be suspended by the command suspstop, reactivated by actstop, or deleted by delstop. If a time breakpoint is suspended when it normally would be trapped, and later reactivated, it will be trapped just before the execution of the next event.

Example

ODB> tstop 1
Added breakpoint #8: stop at time = (1) sec.

ODB> tstop 1.5
Added breakpoint #9: stop at time = (1.5) sec.

ODB> status

Breakpoints :
          8)  stop at time = (1) sec.
          9)  stop at time = (1.5) sec.


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

本站文档由 北京智网畅联科技有限公司 整理、翻译并提供 · Documentation compiled and provided by Beijing ZNetLink Technology Co., Ltd.

交流群 · QQ Group:OPNET/智网妙算网络仿真交流群(群号 486383494)

原文档 © 2017 Riverbed Technology · 本站为公益翻译,由 AI 辅助完成,请仔细甄别

Original documentation © 2017 Riverbed Technology. Community translation, AI-assisted. Contact: jiazequn@znetlink.com