https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64478
--- Comment #16 from Eric Botcazou <ebotcazou at gcc dot gnu.org> --- > you could avoid that scenario by probing say 4K of stack in __gnat_malloc ? No, the stack checking model is to probe sufficiently ahead in the user code by means of -fstack-check but not in the run time. Instead the run time should have a bounded stack usage and avoid calling malloc in these scenarios.
