Building Distributed
Applications
Using the Progress AppServer
Basic Tasks
To execute a remote debugging session you must both invoke the Debugger process and set an initial breakpoint from within your remote 4GL code. For more information on general debugging tasks, such as using the Debugger window and exiting the Debugger process, see the Progress Debugger Guide. This section describes the basic tasks required to initiate remote debugging.
Invoking the prodebug Process
To debug using remote debugging, you must explicitly invoke the debugger using the methods of the DEBUGGER system handle executed from an AppServer session. For more information on the DEBUGGER system handle, see the Progress Debugger Guide and the reference entries for the handle, its methods, and its attributes in the Progress Language Reference .
On UNIX platforms, the Debugger process (
prodebug
) runs as a Motif application, and it requires setting either the PDDISPLAY or DISPLAY environment variable. These variables tellprodebug
where to realize its Debugger window. Because of howprodebug
starts, the environment variable must be set before the AppServer is started. That is, as part of the startup process for an AppServer, the Application Server process inherits the environment variables set up for the Application Broker. Similarly, when the Application Server process starts upprodebug
,prodebug
inherits these same environment variables, including PDDISPLAY and DISPLAY, from the Application Server process.Establishing an Initial Breakpoint
With remote debugging, you must programmatically set an initial breakpoint in the 4GL code by using the SET-BREAK( ) method of the DEBUGGER handle. For information on the DEBUGGER handle, see the Progress Debugger Guide and the Progress Language Reference .
The following example shows how to use the INITIATE( ) and SET-BREAK( ) methods for the DEBUGGER handle.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |