Kbase P128506: Remote debugger only generates source debug listings in the working dir
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/23/2010 |
|
Status: Unverified
SYMPTOM(s):
Remote debugger only generates source debug listings in the working dir
"On the fly" remote debugging can only be done if the source code being debugged physically resides in the remote session working directory.
Source code run from a different directory via the PROPATH cannot be debugged and results in error 3071 in the debugger.
No Debugger listing file available for <procedure name>. (3071).
FACT(s) (Environment):
Windows
OpenEdge 10.x
CAUSE:
Bug# OE00164264
FIX:
As a work around, temporarily move the code to be debugged to the working directory of the remote session and debug it from there.
Alternatively, compile the code and generate a debug listing (*.cmp) file with the compiler DEBUG-LIST option. Provided the debugger "Debug Listing Directories" includes the directory where the remote *.cmp file ( and the source file) exist, the debugger will display the source listing.