ModelSim SE User's Manual - Electrical and Computer Engineering

Breakpoints
The Tcl Debugger UM-495
There are seven possible debugger states, one for each button and an `idle' or `waiting' state
when no button is active. The button-activated states are:
Button Description
Stop stop after next expression, used to get out of slow/fast/nonstop
mode
Next execute one expression, then revert to idle
Slow execute until end of procedure, stopping at breakpoints or when
the state changes to stop; after each execution, stop for ’delay’
milliseconds; the delay can be changed with the ’+’ and ’-’
buttons
Fast execute until end of procedure, stopping at breakpoints
Nonstop execute until end of procedure without stopping at breakpoints or
updating the display
Break terminate execution of current procedure
Closing the debugger doesn't quit it, it only does `wm withdraw'. The debugger window
will pop up the next time a prepared procedure is called. Make sure you close the debugger
with Debugger > Close.
To set/unset a breakpoint, double-click inside the listing. The breakpoint will be set at the
innermost available expression that contains the position of the click. Conditional or
counted breakpoints aren’t supported.
The Eval entry supports a simple history mechanism available via the and
keys. If you evaluate a command while stepping through a procedure, the
command will be evaluated in the context of the procedure; otherwise it will be evaluated
at the global level. The result will be displayed in the result field. This entry is useful for a
lot of things, but especially to get access to variables outside the current scope.
ModelSim SE User’s Manual