Catching out of stack errors?

[Alf Christophersen]

Could it be possible to stop execution when a new call obviously will trash
the limit of stack size and then report the case? Eg. have a security zone
below total size of stack and report if that limit has passed, with the
option to continue execution (which I guess in most cases will lead to an
unhandled out of stack error and full stop of program.

I got a strange out of stack error today and wanted to find how it happened
in case errors in input data triggered it. (The third time I ran the
program, the error did not occure. Strange)

[admin]

Hi,

Alf Christophersen wrote:
> Could it be possible to stop execution when a new call obviously will
> trash the limit of stack size and then report the case? Eg. have a
> security zone below total size of stack and report if that limit has
> passed, with the option to continue execution (which I guess in most
> cases will lead to an unhandled out of stack error and full stop of
> program.
>
> I got a strange out of stack error today and wanted to find how it
> happened in case errors in input data triggered it. (The third time I
> ran the program, the error did not occure. Strange)

I think you can simply try to identify this error changing the stack size from
the "Project/Options.../Linker/Memory size/Min-Max stack size".

--
Best regards...

Fabio Dell'Aria.
----------------
http://www.eurekalog.com
Catch every BUG, every time!