Kbase P128293: Debugger fails to start with one character message
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
2/4/2010 |
|
Status: Verified
SYMPTOM(s):
Attempting to launch Debugger via Procedure Editor
Using Ctrl-F4 or -debugalert stack trace to launch
When opening the debugger, after the splash screen appears it displays a single letter (usually T) and error 4106
Unable to startup PROGRESS Debugger. (4106)
JAVA settings in the Windows Registry are correct
Process Monitor (from Microsoft Sysinternals) shows that PROWIN32.EXE reads the correct path in the JAVA\JREHOME setting
Process Monitor (from Microsoft Sysinternals) shows that PROWIN32.EXE uses the incorrect JREHOME setting when trying to launch the debugger
prowin32.exe 3656 QueryOpen E:\bin\java PATH NOT FOUND
prowin32.exe 3656 QueryOpen E:\bin\java.exe PATH NOT FOUND
prowin32.exe 3656 CreateFile E:\bin\java PATH NOT FOUND Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: N, ShareMode: Read, Write, AllocationSize: n/a
Debugger works if PROWIN32.EXE is launched via Dependency Walker's Profile function
Debugger for OpenEdge 10.1B installed on the same machine works as expected
Debugger enabled with ProDebugEnable -enable-all.
Debugger invoked within 4GL code as follows:
DEBUGGER:INITIATE().
DEBUGGER:SET-BREAK().
When debugger is started first and then attached to a procedure, it does not fail.
FACT(s) (Environment):
OpenEdge 10.1C
All Supported Operating Systems
CAUSE:
Bug# OE00163599
CAUSE:
Failure to start the debugger sometimes may result in a one letter message (usually T) but the message isn't necessarily the problem. The most likely problem which was identified is that an internal (untrapped) error occurred executing the getJavaDir system call.
The message is actually corrupted because OpenEdge is internally using the wrong API call to convert it to text.
FIX:
Upgrade to OpenEdge 10.1C02 or later