From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.4 X-Google-Thread: 103376,872c9f672f291e9b X-Google-Attributes: gid103376,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!proxad.net!feeder1-2.proxad.net!213.200.89.82.MISMATCH!tiscali!newsfeed1.ip.tiscali.net!newsfeed00.sul.t-online.de!t-online.de!newsfeed.icl.net!newsfeed.fjserv.net!newsfeed.arcor.de!newsspool2.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 14 Nov 2007 11:05:56 +0100 From: Georg Bauhaus User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: GNAT and -fstack-check, does it work? References: <47375ee3$0$27835$39db0f71@news.song.fi> <20071114104918.248861fb@cube.tz.axivion.com> In-Reply-To: <20071114104918.248861fb@cube.tz.axivion.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <473ac886$0$4365$9b4e6d93@newsspool4.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 14 Nov 2007 11:05:58 CET NNTP-Posting-Host: aabb7521.newsspool4.arcor-online.net X-Trace: DXC=PEg`De^jiBR1`E>oC;JXEZ4IUKRURQI3ae_Ig\PCY\c7>ejVX3LXk?fGK>SP;BTkkibYjR^ X-Complaints-To: usenet-abuse@arcor.de Xref: g2news1.google.com comp.lang.ada:18364 Date: 2007-11-14T11:05:58+01:00 List-Id: Stefan Bellon wrote: > On Sun, 11 Nov, Niklas Holsti wrote: > >> - Have you had problems like those described in bug 13757? >> Do you know if that bug affects GNAT? > > We have never used -fstack-check with C code, I'm afraid. -fstack-check and then calling C functions caused me trouble a few years ago. Will not using -fstack-check be o.K. with Ada programs in case off-bound access to local arrays (Strings, whatever) will cause SIGSEGV instead of raising an occurrence of expception Storage_Error? Will it be o.K. for GNAT compiled Ada programs to cause segmentation violations instead of storage error when some recursion needs to be run more often than preset stack bounds will permit? I don't want to start turning all local arrays into pointers just because of an unclear situation with -fstack-check. I also do not like an implementation that is in the way of recursive subprograms. If I could afford dropping recursion (and other features of Ada), I'd be using SPARK. But I need Ada for writing general purpose programs.