The Debugger is an integral component of Progress Developer Studio for OpenEdge. It is an interactive tool that provides a full set of tools for testing and debugging programs. It works directly with the ABL Editor, making it easy to identify and fix problems as you work.
The following are the key features of the debug launch configurations provided in the Progress Developer Studio for OpenEdge:
AppServer and WebSpeed debugging - Progress Developer Studio for OpenEdge supports debugging of remote and local AppServer and WebSpeed instances.
Attachable Debugger - The debug launch configuration type allows you to attach the Debugger to an external AVM (which can be an ABL client, a WebSpeed agent, or an AppServer running on the same machine or a remote machine).
AppServer pass-through - You can debug a remote procedure from within Progress Developer Studio for OpenEdge, during pass-through, without having to set breakpoints in the remote procedure code.
SpeedScript debugging - Progress Developer Studio for OpenEdge allows you to debug .w files that are generated from HTML files in a SpeedScript editor.
Standalone Debugger functionality - Progress Developer Studio for OpenEdge provides all the debugging features that are available with the standalone OpenEdge Debugger.
You can use the Debugger in Progress Developer Studio for OpenEdge to run multiple debugging sessions. Each session uses a dedicated instance of the OpenEdge runtime engine, and provides these benefits:
Debugging multiple programs simultaneously, whether the programs are in the same project or in different projects.
Debugging multiple instances of the same program.
Editing the source code using all Editor features, while a debugging session is active.
Stepping through the code, line by line, or stop at specified lines and then resume execution from those points.
Examining data from the procedure you are running, including the names and contents of variables it defines.
Attaching the Debugger to a running process.
Debugging programs running on a remote machine.
Debugging AppServer and WebSpeed instances running on a remote machine or a local machine.
The standalone OpenEdge Debugger
In addition to the Debugger provided by Progress Developer Studio for OpenEdge, OpenEdge provides a standalone Debugger that runs with any OpenEdge application.
To launch the standalone OpenEdge Debugger, select Debugger from the Progress OpenEdge program group on the Windows Start > Programs menu. For more information about the standalone OpenEdge Debugger, see OpenEdge Development: Debugging and Troubleshooting in the Product Documentation section of the Progress Software Developer's Network Web site.
Note: You must use the standalone OpenEdge Debugger for debugging an AppServer version prior to 11.0.
For the purposes of this online help, however, all references to "the OpenEdge Debugger" or "Debugger" pertain to the Debugger in Progress Developer Studio for OpenEdge.
AppServer and WebSpeed debugging - Progress Developer Studio for OpenEdge supports debugging of remote and local AppServer and WebSpeed instances.
