Try OpenEdge Now
skip to main content
Debugging and Troubleshooting
OpenEdge Debugger : Debugger Window and Files : Debugger toolbar buttons
 

Debugger toolbar buttons

The Debugger toolbar contains shortcut buttons for frequently used menu options. The following table describes the toolbar buttons.
Table 11. Toolbar buttons
Button
Action
(Open)
Displays the Open dialog box, which lets you open a procedure file. For more information, see Open dialog box.
(Step Into)
Executes the next statement in a procedure. If the statement calls a subprocedure or causes a trigger to execute, the Debugger steps into the subprocedure or trigger and stops at the first executable line of code. The trigger or subprocedure is now the current procedure, and you can continue execution from the current stopping point.
Note: The Debugger does not step into the destructor method of an object that has been automatically deleted by garbage collection, unless the destructor contains a breakpoint. In cases where the object is explicitly deleted by means of the DELETE OBJECT statement, the Debugger does step into the destructor.and Step Into command
(Step Over)
Executes the next statement in a procedure. If the statement calls a subprocedure or causes a trigger to execute, the Debugger executes the trigger or subprocedure without stepping into it and stops at the next executable line of code. If the Debugger encounters a breakpoint in a subprocedure or trigger, execution stops at the breakpoint, the executing subprocedure or trigger becomes the current procedure, and you can continue execution from the current breakpoint.
Note: After stepping over a statement, if the next statement is in a destructor method for an object that has been deleted, the Debugger does not stop in the destructor unless the destructor contains a breakpoint. This is true whether the object is deleted automatically by garbage collection or explicitly by means of the DELETE OBJECT statement.
(Step Out)
Continues execution until the current procedure ends, returning control to the calling procedure. The execution pointer is at the next line of the calling procedure. If the Debugger encounters a breakpoint or interrupt before returning to the calling procedure, the Debugger cancels the command. The execution pointer is at the break or interrupt line. If issued from the top-level procedure on the ABL call stack and the Debugger encounters no breakpoints or interrupts before the procedure ends, the debugging session ends. The exception is if you start the Debugger with -debug, in which case the Debugger has control, waiting for you to launch a new ABL program.
(Continue)
Continues execution of the specified procedure until it encounters a breakpoint, an interrupt, or the end of the procedure.
(Stop)
Immediately terminates the executing application as if it invoked the ABL STOP statement at the current break or interrupt point, and rolls back uncommitted changes in the current transaction.
(Stop Animation)
Turns off animated stepping. Appears only when animated stepping is in progress.
(Interrupt)
Interrupts and halts an executing procedure and gives control to the Debugger without setting a breakpoint.
(Help Topics)
Displays information about Debugger window components.