P
Paul Clare
Guest
Hi James, I believe the debug list is generated from the r-code, since you are using Developer Studio and the code is compiled. In this case it will need to be able to find the source files in the propath. It might be worth checking your debug configuration to be sure it's configured as you expect? I tested debugging a simple piece of code in 11.2 and 11.3 and it seemed to work from me. From the debugging and Troubleshooting manual: 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.
Continue reading...
Continue reading...