error 667

[mosh1]

Hi! I start getting err 667 in Clipper 5.2 application (there is no FW only objects library), Causeway linker.

OCLONE (0) Unrecoverable error 667: Eval stack fault

please help

[Antonio Linares]

Time to migrate to Harbour

[driessen]

I agree with Antonio.

You'd better migrate to Harbour because Clipper applications are 16-bits and they won't run on the current PC's which are 64-bis.

[Badara Thiam]

Hello

Here is the NG help for this error :
---

Explanation: The evaluation stack (containing LOCALs, etc.) and/or
Memvar table has been exceeded, causing an attempt to access a locked VM
segment in near memory.

Action: Some suggestions to resolve this problem are:

1. Decrease the stack or PROCEDURE DEPTH setting for the linker.

2. Decrease the number of LOCAL, STATIC or PRIVATE variables in use at
one time. i.e., use arrays instead of individual variables.

3. Decrease the number of ITEMS allocated if using ITEM.API of
CA-Clipper.

4. Free more conventional memory for use by the VM System.

Note: There could be an error in the runtime error handler.

See Also: Error 650.

[Badara Thiam]

650 Out of stack space

Explanation: stack space is exhausted.

Action: Some suggestions to resolve the problem are:

1. Use STACK or PROCEDURE DEPTH command to instruct the linker to
increase the stack space at link time.

2. check for recursion. Some modifications to the CA-Clipper
errorsys.prg may cause a recursive call, which will exhaust the call
stack.

3. try using the default CA-Clipper errorsys.prg if the errorsys.prg was
modified to test for runaway recursion caused by an error occurring
while attempting to handle an Error Object.

4. Check for UDFs/.PRGs that have the same name as an internal
CA-Clipper function.

5. Check for use of an incorrect or invalid version of the Errorsys.prg,
i.e., the Summer '87 CA-Clipper Errorsys.prg does not use an Error
object.

[James Bott]

If you are using a lot of PUBLICs and PRIVATEs, I suggest converting as many as possible to LOCALs.

Regards,
James