Kbase P141938: OE client terminates abruptly without error when stepping into RUN statement for procedure with DATA
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/03/2011 |
|
Status: Verified
SYMPTOM(s):
OE client terminates abruptly without error when stepping into RUN statement for procedure with DATASET output parameter
OE client terminates abruptly without error when stepping over RUN statement for procedure with DATASET output parameter
AVM terminates unexpectedly when debugging code in OpenEdge Architect
AVM terminates unexpectedly when debugging code in StandAlone Debugger
A socket error occurred while trying to communicate with the Debugger; Error code is: <error code>. (11671)
A socket error occurred while trying to communicate with the Debugger; Error code is: 10053. (11671)
Error can occur when AVM terminates:
SYSTEM ERROR in a .NET event handler
Lost connection to Progress Debugger. (4348)
A socket error occurred while trying to communicate with the Debugger; Error code is: <error code>. (11671)
A socket error occurred while trying to communicate with the Debugger; Error code is: 10053. (11671)
Sample code to reproduce this problem:
/* caller.p */
DEFINE TEMP-TABLE ttCust
FIELD CustNum AS INTEGER FORMAT ">>>>9"
FIELD Name AS CHARACTER FORMAT "x(30)".
DEFINE DATASET dsetCustomer FOR ttCust.
DEFINE VARIABLE cSessionID AS CHARACTER NO-UNDO.
RUN called.p ( OUTPUT DATASET dsetCustomer,
OUTPUT cSessionID ).
/* called.p */
DEFINE TEMP-TABLE ttCust
FIELD CustNum AS INTEGER FORMAT ">>>>9"
FIELD Name AS CHARACTER FORMAT "x(30)"NT>.
DEFINE DATASET dsetCustomer FOR ttCust.
DEFINE OUTPUT PARAMETER DATASET FOR dsetCustomer.
DEFINE OUTPUT PARAMETER pcSessionID AS CHARACTER INITIAL ? NO-UNDO.
DEFINE VARIABLE iCount AS INTEGER NO-UNDO.
DO iCount = 1 TO 100:
END..
FACT(s) (Environment):
Code itself executes correctly when run - form is visualized as expected
No protrace files are generated
ADPlus does not generate any 2nd-chance exception logs to indicate a crash
Progress portion of the stack trace from the ADPlus 1st-chance exception log appears to show a normal shutdown:
prow32.dll!_drexit() + 0x4eb bytes C
prow32.dll!_rnrq_last() + 0x80 bytes C
prow32.dll!_rninterpret() + 0x24 bytes C
prow32.dll!_umeDispatchEvent() + 0xdd1 bytes C
prow32.dll!_wwRunDispatcher() + 0x1cf bytes C
prow32.dll!_pdchkstepping() + 0xa1 bytes C
prow32.dll!_drmain() + 0x467 bytes C
Problem was introduced in OpenEdge Release 10.0B
Problem can be reproduced with the StandAlone debugger when the Parameters tab is selected upon stepping into the called procedure.
OpenEdge 10.0B
OpenEdge 10.1x
OpenEdge 10.2A
Windows
CAUSE:
Bug# OE00181505
FIX:
Upgrade to OpenEdge Release 10.2B or later
FIX:
To work around this issue in the StandAlone Debugger, ensure that the "Parameters" pane is not visible when stepping into the called procedure.
To work around this issue in the OEIDE debugger, use the de-select the "Show Parameters" option in the Filters for the Variables view