A Clipper Question (668)

[rdonnay]

Does anyone remember how to resolve 668 Eval Stack errors in Clipper?

I received emails and phone call from a programmer who is having this problem with and old Clipper/FiveWin app because I made a reference to a FIX668.PRG file in an old Memory Management seminar that he found online. I searched everywhere for this file and can't find it.

Can anyhelp help with this?
I haven't worked in Clipper in over 10 years.

[Auge_Ohr]

668 EVAL STACK FAULT

Explanation: The evaluation stack expanded into a locked VMM
segment. The CA-Clipper VM System will use the DGROUP Free Space when
conventional DOS memory is very low.

Action: Free up conventional DOS memory by reducing the
application's load size and/or increasing free DOS memory as reported by
DOS's MEM.EXE command.

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

See Also: Error 650.

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.

[rdonnay]

Thanks Jimmy.

I already told him about changing the STACK or PROCEDURE DEPTH size.
He tried that with Blinker but it didn't work for him.

I'll send along your info to him.

[Cliff Wiernik]

Enclosed is a zip of the dgroup files I have and used.

[rdonnay]

I forgot about DGROUP.ZIP.

Thanks for that.