error 667

error 667

Postby mosh1 » Wed Sep 18, 2013 2:37 am

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
mosh1
 
Posts: 129
Joined: Sun Oct 09, 2011 3:50 pm

Re: error 667

Postby Antonio Linares » Wed Sep 18, 2013 8:08 am

Time to migrate to Harbour :-)
regards, saludos

Antonio Linares
www.fivetechsoft.com
User avatar
Antonio Linares
Site Admin
 
Posts: 35253
Joined: Thu Oct 06, 2005 5:47 pm
Location: Spain

Re: error 667

Postby driessen » Wed Sep 18, 2013 3:44 pm

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.
Regards,

Michel D.
Genk (Belgium)
__________________________________________________________________________________________
I use : FiveWin for (x)Harbour v. 17.12 - Harbour 3.2.0 (March 2017) - xHarbour Builder (May 2017) - Bcc7
User avatar
driessen
 
Posts: 1122
Joined: Mon Oct 10, 2005 11:26 am
Location: Genk, Belgium

Re: error 667

Postby Badara Thiam » Thu Oct 03, 2013 3:36 pm

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
http://www.icim.fr
User avatar
Badara Thiam
 
Posts: 146
Joined: Tue Oct 18, 2005 10:21 am
Location: France

Re: error 667

Postby Badara Thiam » Thu Oct 03, 2013 3:38 pm

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.
Badara Thiam
http://www.icim.fr
User avatar
Badara Thiam
 
Posts: 146
Joined: Tue Oct 18, 2005 10:21 am
Location: France

Re: error 667

Postby James Bott » Wed Oct 16, 2013 9:50 pm

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

Regards,
James
User avatar
James Bott
 
Posts: 4330
Joined: Fri Nov 18, 2005 4:52 pm
Location: San Diego, California, USA


Return to FiveWin for CA-Clipper

Who is online

Users browsing this forum: No registered users and 2 guests