Kbase P69853: Workaround: Progress session crashes with memory errors when
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
13/07/2007 |
|
Status: Unverified
FACT(s) (Environment):
Progress 8.3E
FACT(s) (Environment):
Progress 9.x
FACT(s) (Environment):
OpenEdge 10.0A
SYMPTOM(s):
Progress session crashes with memory errors when passing a parameter with a long value to an INPUT PARAMETER with the wrong datatype
Depending on the length of the value, Progress can display first errors dependant on the datatype of the INPUT PARAMETER followed by errors 5729 and 2570, and then the memory errors
Incompatible datatypes found during runtime conversion. (5729)
Procedure <proc> sent sub-procedure <proc> mismatched parameters. (2570)
The instruction at "<memory address>" referenced memory at "<memory address>". The memory could not be "read".
Click on OK to terminate the program
Click on CANCEL to debug the program
The instruction at "<memory address>" referenced memory at "<memory address>". The memory could not be "read".
Click on OK to terminate the program
//=====================================================
PROGRESS stack trace as of Wed Feb 18 16:28:30 2004
//=====================================================
Exception code: C0000005 ACCESS_VIOLATION
Fault address: 10194DA8 01:00193DA8 c:\progress\dlc91d\BIN\prow32.dll
Registers:
EAX:6C6C6F63
EBX:00000000
ECX:00E19465
EDX:00000003
ESI:00133C42
EDI:77FCF010
CS:EIP:001B:10194DA8
SS:ESP:0023:0012FB6C EBP:0012FC1C
DS:0023 ES:0023 FS:0038 GS:0000
Flags:00010206
Call Stack:
Address Frame
10194DA8 0012FC1C fmconv+5F9
20796C6E 6F206572
Reducing the length of the parameter will produce the expected Progress error messages and avoid the session crash
CAUSE:
No known cause at time of writing
FIX:
Correct the datatype of the INPUT PARAMETER to match that of the value being passed into it