Try OpenEdge Now
skip to main content
Debugging and Troubleshooting
OpenEdge Debugger : Debugger Window and Files : Debugger files : Procedure files and listing generation : Debug listing generation from r-code
Debug listing generation from r-code
When your application runs an r-code file, OpenEdge attempts to provide the debug listing for it by searching the PROPATH for the associated source file (.p, .w). The r-code contains references to all associated source, include, and debug listing files, as well as its cyclic redundancy check (CRC) value.
If OpenEdge finds the source file associated with an r-code file, it compares the CRC value of the source file with the corresponding CRC value stored in the r-code. If the CRC values do not match, OpenEdge displays a warning message and continues using the file with a bad CRC value.
You can step through r-code for which the source code is unavailable; however, the Debugger cannot display the source code in the source code pane. In this case, the Debugger displays the procedure name and line number in the status bar.