Kbase P102916: FIRST-OF causes core dump if BREAK BY is based on CAN-FIND
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/10/2006 |
|
Status: Unverified
FACT(s) (Environment):
UNIX
Progress 9.1E
SYMPTOM(s):
FIRST-OF causes core dump
Using CAN-FIND function in BREAK BY clause
SYSTEM ERROR: Memory violation. (49)
Stack trace on Solaris 64-BIT reads:
(4) _setitimer() +0xb4 from: /usr/lib/sparcv9/libthread.so.1
(5) _sema_post() +0x530 from: /usr/lib/sparcv9/libthread.so.1
(6) _sema_post() +0x6f4 from: /usr/lib/sparcv9/libthread.so.1
(7) recGetLONG() +0x74 from: /mls01/progress/dlc91e/bin/_progres
(8) copditm() +0x4 from: /mls01/progress/dlc91e/bin/_progres
(9) fmEGLOB() +0x140 from: /mls01/progress/dlc91e/bin/_progres
(10) fmeval() +0x928 from: /mls01/progress/dlc91e/bin/_progres
CAUSE:
This is a known issue being investigated by Development
FIX:
Workaround:
Use USE-INDEX to force the use of a specific index in the CAN-FIND function in the BREAK BY.