I've been having the most strange error since a couple of days ago:
LOCKERRHAN (0) Unrecoverable error 650: Processor stack fault
I'm using
- CLIPPER 5.2e Intl version with EXOSPACE 1.0
- my own LIB made of standard Clipper code only
on
- DOS 5.0, Novell Netware Lite 1.1
I can't find this error description on Norton Guides.
My main machine is a P166 - 24Mb Ram. This is the machine I use to write,
compile and test.
I've tested the compiled EXEs on the other two computers on the network, but
they behave the same, so this shouldn't be a real processor problem...
Also, this error happens in different (random) places of the programs.
Sometimes right after startup, other times it lets me choose menu options,
edit fields, and then it goes down showing this error message.
I suspect this error is made up by something during compiling or linking,
that shows only at runtime, since I have near 20 Clipper EXEs on working
versions, that run perfectly on any one of the 3 machines.
The difference betwen the working versions and the developping versions -
where the error shows - is only some corrections and enhancements made on
standard Clipper code, that compiles fine, showing no error at all!
Does anybody ever had this kind of error ?
Any help will be mostly appreciated. Thank you very much.
António Vila-Chã
Viana do Castelo
Portugal
Check this thread:
Subject: Clipper5.3b + Blinker5.0 (Error 667:Eval stack fault)
Date: Mon, 19 Jun 2000 13:46:15 GMT
And try this:
PROCUDERE Test()
Test()
RETURN
Regards,
Wong
Internal error 650 means that you've run out of stack space. Here's a longer
description of the problem:
,----[ Excerpt from the MrDebug Norton Guide ]
| What is a Unrecoverable Error 650 - Processor Stack Overflow?
| The stack has blown!
| ------------------------------------------------------------------------------
|
| Basically the most likely cause of this is Recursion.
|
| Normally 8 out of 10 cats owners who expressed a preference said that
| their UE 650's occurred because of an error in their error systems. An
| error occurred in the error system and so the error system was called,
| the error occurred again and then the error system was called etc.
|
| This may be resolved by correcting the error within the error system and
| re-compiling, linking and running the program again.
|
| On the odd occasion where this is not the problem another explanation
| could be that there is simply not enough space Reserved for the CPU
| Stack. If this is the case, then you may increase the amount of space
| being reserved for the CPU stack by allocating a larger stack space using
| your linker stack command.
|
| Please remember that when you increase your stacks, you are lowering the
| amount of DS available and hence reducing the amount of space for the
| Memvar table and the Eval stack to grow into which could force a
| different problem to appear.
`----
<URL:http://www.hagbard.demon.co.uk/clipper-faq/clipper-5.html#ss5.6> also
briefly covers this.
> The difference betwen the working versions and the developping versions -
> where the error shows - is only some corrections and enhancements made on
> standard Clipper code, that compiles fine, showing no error at all!
Code that can cause an IE650 will compile without problems. IE as a problem
at runtime, not compile time.
--
Take a look in Hagbard's World: | w3ng - The WWW Norton Guide reader.
http://www.hagbard.demon.co.uk/ | eg - Norton Guide reader for Linux.
http://www.acemake.com/hagbard/ | weg - Norton Guide reader for Windows.
Free software, including........| dgscan - DGROUP scanner for Clipper.
Last january I added errorsys.prg to my main LIB, with alert buttons
translated to portuguese. One of them had a small mistake, and that was
causing the problem.
I'll keep trying to find why this error only showed in the last few days,
although I've been working my code almost every day since that errorsys was
changed.
Regards,
António Vila-Chã