Kbase P132053: Dynamic CALL object crashes when CALL-NAME not set
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/5/2008 |
|
Status: Unverified
FACT(s) (Environment):
All Supported Operating Systems
Progress 9.1D
OpenEdge 10.0x
OpenEdge 10.1A
SYMPTOM(s):
Dynamic CALL object crashes when CALL-NAME not set
Invoking CALL object GPFs when CALL-NAME not set
Stack trace from _progres/prowin32 reads:
rnrun
rnexec_entry
rninterpret
umeDispatchEvent
CAUSE:
Bug# OE00148437
CAUSE:
This problem occurred before a check was put in place to ensure that the CALL-NAME attribute is not NULL. This attribute must be set for the CALL to function properly, however it should not cause a crash when it is absent.
FIX:
Upgrade to OpenEdge 10.1C.
To workaround this issue in previous versions/releases, specify the CALL-NAME before executing the INVOKE method on the CALL object.