Progress
Debugger Guide
Debug Listing Generation from R-code
If Progress runs the r-code version, Progress tries to locate an existing debug listing for it. The r-code contains references to all associated source, include, and debug listing files, including their cyclic redundancy check (CRC) values. When your application runs an r-code file, Progress attempts to provide the debug listing using this method:
- If the r-code file references a debug listing whose path prefix is compatible with the current operating system, Progress uses the path prefix together with the current PROPATH to locate the file and ensure that the r-code and listing CRC values match.
- If it cannot find the listing file or the CRC values do not match, Progress tries to regenerate the debug listing using the source and include file references stored in the r-code, and saves the new listing as a temporary file.
- If Step 2 fails because a source or include file cannot be found, Progress uses any debug listing found in Step 1 with a bad CRC.
- If the debug listing file cannot be found or created in any form, Progress displays a warning message and continues executing the r-code.
For all file search and creation attempts in the previous steps, Progress verifies each source, include, and debug listing file with the corresponding CRC value stored in the r-code. If the CRC value does not match a located file, Progress displays a warning message and continues using the file with a bad CRC value.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |