Progress
Debugger Guide
Execution Monitoring
The Debugger provides several ways to examine the state of an application.
Code Path Analysis
During procedure execution, the Debugger window displays the listing of the procedure at each breakpoint or stopping point in its execution. A pointer always indicates the next line to execute. At any stopping point, you can display the listing for any procedure file using the FILE command. This provides a convenient way to set breakpoints for any procedure in your environment, whether or not it is called from the procedure you are running.
You can examine the procedure call stack using the SHOW STACK command, and you can navigate the procedure call stack using the UP and DOWN commands. This allows you to examine the current code path back and forth through the active series of procedure calls and triggers starting from the current stopping point.
From the 4GL, you can use the DISPLAY-MESSAGE( ) method of the DEBUGGER handle to display message strings to the Debugger window, indicating the status of the procedure as it executes.
Transaction Monitoring
You can determine the transaction state of your application using the SHOW TRANSACTION command. This tells you whether or not a transaction is active at the current stopping point.
Breakpoint Analysis
You can display the current breakpoint settings using the SHOW BREAKS command. This command lists the breakpoints currently set for all procedures during the session. The listing for each executing procedure also indicates each line where a breakpoint is set when displayed in the Debugger window.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |