DEBUGGER Handle Attributes and Methods
The DEBUGGER handle attributes and methods provide a limited set of capabilities primarily designed to start up and clean up after a debugging session from the 4GL. A few additional capabilities duplicate some basic Debugger commands and provide a means of performing certain debugging tasks that are more convenient from the 4GL.
Table 7–1 lists the function of each DEBUGGER handle attribute.
Table 7–1: DEBUGGER Handle Attributes
Attribute
|
Function
|
TYPE
|
Returns the widget type of the Debugger, the standard value for all system handles, “PSEUDO-WIDGET”.
|
VISIBLE
|
Displays or removes the Debugger window on the screen.
|
Table 7–2 lists the function of each DEBUGGER handle method.
Table 7–2: DEBUGGER Handle Methods
Method
|
Function
|
CANCEL-BREAK( )
|
Removes a specified breakpoint. Provides the function of the Debugger CANCEL BREAK command.
|
CLEAR( )
|
Cancels all breakpoints and logging; clears the listing, command, and data panels; and otherwise returns the Debugger to the state it was in immediately after initialization.
|
DEBUG( )
|
Initializes and immediately gives control to the Debugger in stand-alone mode while the invoking procedure blocks.
|
DISPLAY-MESSAGE( )
|
Displays a character string in the data panel of the Debugger window.
|
INITIATE( )
|
Initializes but does not immediately give control to the Debugger. When the invoking procedure encounters a breakpoint, it gives control to the Debugger in application mode and becomes the current procedure in the Debugger context.
|
SET-BREAK( )
|
Sets a specified breakpoint. Provides the function of the Debugger BREAK command.
|
NOTE: For information on Progress attributes and methods, see the Progress Programming Handbook.
To use any of these attributes or methods within a procedure, except DEBUG( ) or INITIATE( ), you must first initialize the Debugger. That is, you must perform one of the following actions:
- Start the Debugger from the operating system or from the 4GL using the DEBUG( ) method, and then run the procedure from the Debugger using the RUN command.
- Invoke the INITIATE( ) method. Typically, you then set an initial breakpoint to start up the Debugger using the SET-BREAK( ) method.