Try OpenEdge Now
skip to main content
Online Help
Running and debugging ABL programs : Reference : Debugger views : Debug view
 
Debug view
The Debug view shows one or more session trees for each active Debugger session. It also displays all the running agents on the broker which is attached to the Progress Developer Studio for OpenEdge Debugger during remote debugging. It changes dynamically as agents are added or removed from the attached broker.
The Debug view also provides the program execution commands that you use to step through the code.
The Debug perspective includes the Debug view by default. If the view is not open, select Window > Show View > Debug from the Debugger perspective to display it.

Session tree Debug view

The session shows the contents of the ABL stack trace (lines marked with ) for the currently executing procedure in each active debugging session. In its initial state, the session tree shows the following entries:
  Project name[OpenEdge Application]
     Source file name at localhost
       OpenEdge Runtime (suspended)
         Source file path and current line number
     OpenEdge-install-dir\bin\prowin32.exe date and time
The stack trace changes dynamically as you step through the code, adding and removing entries that indicate the execution sequence of the current procedure. The current line appears at the top of the stack.
You can investigate the code associated with a line of the stack trace by clicking on the stack trace line. The ABL Editor window containing that code becomes active, and the Variables view, the Expressions view, and the Dynamic Objects view show data values as they are immediately preceding execution of the selected line.
See Using the Debug view and stack trace for more information.

Program execution commands

The following commands are available on the Debug view toolbar and context (right-click) menu:
Command
Action
Step Into
Execute the current line and continue until reaching 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.
See also the information about garbage collection in Code stepping.
Step Over
Execute the current line and continue until reaching 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, step "over," not "into," the subprocedure or trigger.
Step Return
Execute the current line and continue either until reaching either a breakpoint, or until the current procedure ends and returns control to the calling procedure.
Resume
Execute the current line and continue without interruption until reaching either a breakpoint or the end of the program.
Suspend
Interrupt execution following completion of the current instruction and give control to the Debugger at the next executable statement.
Also, suspend the attached AVM.
Terminate
Interrupt execution and end the Debugger session.
Remove All Terminated Launches
Clear the Debug view of session trees that are no longer active.
Disconnect
Disconnect from the attached AVM and stop receiving notifications from the running external AVM.