Progress
Debugger Guide
Listing Panel
The listing panel displays the debug listing for both the current procedure and any other procedure whose listing you want to see. The debug listing is a specially prepared source listing that allows you to more easily set breakpoints and follow the course of procedure execution in an application. This listing also provides a point of reference for specifying arguments to Debugger commands.
Debug Listing
The debug listing is an expanded listing file that Progress creates during procedure compilation. This file contains a line-numbered listing of the procedure with the text of any embedded preprocessor include files, names, and parameters inserted. For more information on debug listing files and how they are generated, see Debugger Files."
Listing Display
The Debugger displays the listing for the executing procedure each time it receives control (for example, at a breakpoint). During Debugger control, you can also display the debug listing for any other active or inactive procedure in the listing panel using the UP, DOWN, and FILE commands.
If the Debugger cannot find the debug listing for the current or specified procedure, it tries to generate it from the procedure source code. If the Debugger can only find the r-code for the procedure, each time it would normally display the listing, the Debugger leaves the listing panel unchanged and displays a message that the listing is not available. For more information on how Progress searches for debug listing files, see Debugger Files."
Listing Indicators
When the panel displays the listing for the current procedure, it also displays up to two listing indicators: a line pointer that shows the next line to execute and a breakpoint indicator that shows each line where a breakpoint is set. The line pointer is an arrow (
in Windows;
=>
in Motif) that points to the line number of the next executable line. The breakpoint indicator in Windows is a thick-lined octagon and in Motif is an asterisk (*), placed to the left of the line number of each line where a breakpoint is set.NOTE: In this manual, all example listing panel code fragments use the Motif line pointer (=>
) and breakpoint indicator (*).If you use the FILE command to list a procedure that is not in the Debugger context, breakpoint indicators appear on the lines where breakpoints are set, whether or not the lines are executable. If the procedure is in the Debugger context, all breakpoint indicators are listed on effective executable lines, whether or not they were set on those lines. If you list a procedure in the Debugger context other than the executing procedure, the Windows line pointer becomes a box arrow to indicate that it is waiting on a subprocedure executed from the indicated line; the Motif line pointer becomes a double arrowhead (
>>
) for the same purpose.Listing Name
The Debugger window labels the panel with the name of the procedure whose listing it is displaying. For example, the listing panel in Figure 4–1 and Figure 4–2 displays the listing for
r-runper.p
.NOTE: Any procedure that you run in application mode from a Procedure Editor buffer is displayed using a filename with a.ped
extension. This is the filename for a temporary procedure file where the Editor writes the 4GL contents of the buffer. The names of temporary procedure files written by the AppBuilder have a.ab
extension.Text Selection
The Debugger window provides a text cursor that you can use to select lines and parts of lines to set breakpoints and to specify other arguments to Debugger commands. For more information on using text selections in the listing panel to enter Debugger commands, see Running a Debugging Session."
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |