Debugging a Discrete Event Simulation
Note: Unless otherwise noted, the term “simulation” can mean a simulation involving only Riverbed Modeler or a cosimulation with an external system.
Riverbed Modeler supports two levels of debugging: object and source. Both levels are available from either the GUI or the command line.
Modeler provides a variety of means for tracking memory usage and locating memory leaks, as described in Tracking Memory Usage.
To get maximum benefit from the Modeler debugging tools, follow these Debugging Hints.
Object-Level Debugging Using ODB
Object-level debugging helps you solve problems with the design of your model. It uses the OPNET Debugger (ODB), which is part of every simulation that uses a development kernel. ODB gives you interactive control of a simulation, letting you issue commands to pause and resume execution, get detailed information about simulation entities (events, objects, packets, and processes), and so on.
See “Simulation Debugger (ODB)” on page 39 for information on how ODB can be used to locate design errors within a simulation, including a command reference and sample sessions.
Source-Level Debugging Using ODB and a Source-Level Debugger
Source-level debugging helps you solve problems with the implementation of your model. On Linux and Windows, the OPNET Debugger GUI lets you attach an external code debugger to a simulation, giving you access to the source code that implements the simulation. This gives you the following additional benefits over using ODB alone:
- View variable values
- View execution at a more fine-grained level
- Use data-based breakpoints
Some of the problems you can solve with source-level debugging are the following:
- Segmentation violations
- Invalid memory access
- Bus errors
- Program faults
For a description of the GUI interface for source-level debugging:
For a description of source-level debugging from the command line: