While a Debugger session is active, use the following commands on the Debug view toolbar or context (right-click) menu to execute the program incrementally:

  • Step Into —Causes the Debugger to execute the current line and continue until it reaches the next executable statement, which may be in the current procedure, a subprocedure, or a trigger. That statement becomes the current line, and it is not executed until you continue.
  • Step Over —Causes the Debugger to execute the current line and continue until it reaches either a breakpoint, or the next executable statement in the same procedure. Thus, if the current line calls a subprocedure or causes a trigger to execute, the subprocedure or trigger is executed without interruption unless there is a breakpoint. In other words, the Debuggers steps "over," not "into," the subprocedure or trigger.
  • Step Return —Causes the Debugger to execute the current line and continue either until it reaches a breakpoint, or until the current procedure ends, returning control to the calling procedure.
  • Resume —Causes the Debugger to execute the current line and continue without interruption until it reaches either a breakpoint or the end of the program.
  • Suspend —Interrupts execution following completion of the current instruction and gives control to the Debugger at the next executable statement. Also, suspends the attached AVM.
  • Terminate —Interrupts execution and ends the Debugger session.
  • Disconnect —Disconnects the Debugger from the attached (running) external AVM and stops receiving notifications from it.
    Note: These commands are enabled only when a Debugger session is active and, with the exception of the Suspend command, only when an entry in its stack trace is selected.

Garbage collection

For details about the behavior of code-stepping with regard to garbage collection, see Garbage collection in the Debugger.