Re: Can't set executable stack size during compilation

[Mark Lorenzen <mark.lorenzen@gmail.com>]

On 4 Jan., 17:27, Georg Bauhaus <rm.dash-bauh...@futureapps.de> wrote:
> [...]
> FWIW, I made a little test program; I think it is legal
> but it crashes consistently when translated with GNAT/GCC.
> With -fstack-check given, the most unexpected thing to see is a
> segmentation fault!

If the environment task uses too much stack space, it may not be
possible to raise an exception or unwind the raised exception (i don't
know which). Probably because raising or unwinding an exception uses
some stack space itself. See
http://www.adacore.com/wp-content/files/auto_update/gnat-unw-docs/html/gnat_ugn_24.html

[QUOTE]
For the environment task, the stack size depends on system defaults
and is unknown to the compiler. Stack checking may still work
correctly if a fixed size stack is allocated, but this cannot be
guaranteed. To ensure that a clean exception is signalled for stack
overflow, set the environment variable GNAT_STACK_LIMIT to indicate
the maximum stack area that can be used, as in:

SET GNAT_STACK_LIMIT 1600

The limit is given in kilobytes, so the above declaration would set
the stack limit of the environment task to 1.6 megabytes. Note that
the only purpose of this usage is to limit the amount of stack used by
the environment task. If it is necessary to increase the amount of
stack for the environment task, then this is an operating systems
issue, and must be addressed with the appropriate operating systems
commands.
[/QUOTE]

Best Regards,

Mark L