Progress
Debugger Guide
Starting the Debugger from the 4GL
Any technique you use to run the Debugger from the 4GL runs the Debugger in either application or stand-alone mode. (For an introduction to application and stand-alone mode, see Introduction.") Each technique allows your application to interact with the Debugger context in a different way, allowing more or less control of the Debugger from your invoking application. These techniques include:
- Application mode — Executes the INITIATE( ) and SET-BREAK( ) methods in the invoking application. At the first breakpoint specified by a SET-BREAK( ) method, the Debugger runs and takes control with the invoking procedure as the initial procedure in the Debugger context. In effect, the invoking procedure debugs itself. You can also use this technique to implement a Debugger tool that debugs a specified subprocedure under 4GL control, and optionally make the invoking procedure invisible to the Debugger context. This is the technique used by the Procedure Editor and AppBuilder to implement the Debug option of the Compile menu.
- Stand-alone mode (as a tool of your application)— Executes the DEBUG( ) method in the invoking procedure. The invoking procedure blocks until the Debugger returns (exits). In effect, the Debugger runs as a subroutine or tool of the invoking procedure and can only debug procedures that you run from the Debugger. In other words, the invoking procedure is not part of the Debugger context. This is the technique used by the ADE Desktop to invoke the Debugger.
- Stand-alone mode (from the Procedure Editor)— Executes the DEBUG( ) method as part of a two-line procedure in the Procedure Editor. This technique starts the Debugger directly from an Editor buffer without reference to any procedure. In effect, the Debugger runs as a stand-alone tool in the Editor and can only debug procedures that you start from the Debugger.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |