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=-0.9 required=5.0 tests=BAYES_00,FORGED_GMAIL_RCVD,
	FREEMAIL_FROM autolearn=no autolearn_force=no version=3.4.4
X-Received: by 2002:a6b:b281:: with SMTP id b123mr220950iof.39.1549056772776;
        Fri, 01 Feb 2019 13:32:52 -0800 (PST)
X-Received: by 2002:aca:5884:: with SMTP id m126mr293190oib.4.1549056772589;
 Fri, 01 Feb 2019 13:32:52 -0800 (PST)
Path: 
 eternal-september.org!reader01.eternal-september.org!feeder.eternal-september.org!feeder.erje.net!1.eu.feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.am4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!k10no330605itk.0!news-out.google.com!v71ni420ita.0!nntp.google.com!k10no330599itk.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Fri, 1 Feb 2019 13:32:52 -0800 (PST)
In-Reply-To: <q32486$1746$1@gioia.aioe.org>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=85.168.19.89;
 posting-account=O_NgcgoAAABs6pgCjroQBmOBL5ZZGPUc
NNTP-Posting-Host: 85.168.19.89
References: <987a6ff2-32d0-45a0-b90a-be9fbf1ff47b@googlegroups.com>
 <q32486$1746$1@gioia.aioe.org>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3fc8fa43-0e74-4409-9724-0111cb305150@googlegroups.com>
Subject: Re: Yet another gnat bug
From: George Shapovalov <gshapovalov@gmail.com>
Injection-Date: Fri, 01 Feb 2019 21:32:52 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2176
X-Received-Body-CRC: 3312396265
Xref: reader01.eternal-september.org comp.lang.ada:55424
Date: 2019-02-01T13:32:52-08:00
List-Id: <comp.lang.ada>

On Friday, February 1, 2019 at 7:47:39 PM UTC+1, Dmitry A. Kazakov wrote:
> Do not panic. In many cases the bug is triggered by an illegal program.=
=20
> Try an older version of GNAT compiler to find what triggers it. In other=
=20
> cases you can work around it using minor code variations.
Oh, I am far from panic. It is, as I mentioned, already like 3rd project wh=
ere I trigger a similar bug in the space of a week or two. Just, when you f=
inally laid out thing just the way you wanted and then gnat explodes on tha=
t final compile attempt.. Then you get such an expression of frustration :)=
.

Thanks for the advice though! This is pretty much how I handle these. But n=
ice to know I am not alone in this. Well, in fact not so nice - would be ni=
cer if this never happened of course :). But at least reassuring. So thanks=
 again.