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=unavailable autolearn_force=no version=3.4.4
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Simon Wright <simon@pushface.org>
Newsgroups: comp.lang.ada
Subject: Re: Help needed - "Storage_Error stack overflow or erroneous memory
 access"
Date: Mon, 19 Jun 2017 08:03:40 +0100
Organization: A noiseless patient Spider
Message-ID: <ly60fsa27n.fsf@pushface.org>
References: <5a0d60e6-c713-4a83-8c98-81a2af68e75e@googlegroups.com>
	<oi5ldc$d9t$1@dont-email.me>
	<93822692-767f-4546-8e39-9c4b7ceab3e6@googlegroups.com>
	<291a8209-d893-4822-896d-32727d5c9509@googlegroups.com>
	<oi64e9$mji$1@dont-email.me>
	<7132e1a3-6c36-4f53-94d5-f51b18373e20@googlegroups.com>
	<1f3089a8-a304-4be3-ab1d-bff5c5b75a18@googlegroups.com>
	<d02780f5-a4f5-4681-a08a-4fc04fda7b67@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org;
 posting-host="90f53780c2ac5da27dccc79281b58776";
	logging-data="4267"; mail-complaints-to="abuse@eternal-september.org";
	posting-account="U2FsdGVkX19iETt0oKL1EzK3Ux2TgrY2CXNfF+gjNCI="
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.2 (darwin)
Cancel-Lock: sha1:kOl4HyxaAQ+T/COLVpH90jCWJfg=
	sha1:UeP2aT8Vv7uenPXGzIkGXYK367U=
Xref: news.eternal-september.org comp.lang.ada:47003
Date: 2017-06-19T08:03:40+01:00
List-Id: <comp.lang.ada>

Here, on x86_64-apple-darwin16 (macOS Sierra), I get

FSF GCC 7.1.0: compiles OK.
FSF GCC 8.0.0: compiles OK.
GNAT GPL 2016: compiles OK.
GNAT GPL 2017: compiles OK.

But, with FSF GCC 6.1.0,

     1. with frame1;         use frame1;
     2. procedure c0 is
     3.    df : df_t;
     4. begin
     5.    df.center0 (True);
           |
        >>> "" is undefined

     6. end c0;

which is a symptom of an internal compiler error. Perhaps your 6.3.0
problem is related to that.