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:4e0b:: with SMTP id c11-v6mr5871898iob.22.1534069109967; Sun, 12 Aug 2018 03:18:29 -0700 (PDT) X-Received: by 2002:aca:de07:: with SMTP id v7-v6mr357157oig.5.1534069109827; Sun, 12 Aug 2018 03:18:29 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!news.uzoreto.com!weretis.net!feeder6.news.weretis.net!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!w19-v6no290775itb.0!news-out.google.com!c189-v6ni906ith.0!nntp.google.com!w19-v6no290773itb.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sun, 12 Aug 2018 03:18:29 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=121.45.203.80; posting-account=d51RWwoAAADvR-x0zYAtT9z3CRxT1eXo NNTP-Posting-Host: 121.45.203.80 References: <9ebc1079-fcb0-4f63-a56a-9da37c593886@googlegroups.com> <2ed1d5bb-9fb0-4e97-b7c4-454b8692fbd7@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: AdaCore Community 2018 Bugs From: Roger Injection-Date: Sun, 12 Aug 2018 10:18:29 +0000 Content-Type: text/plain; charset="UTF-8" Xref: reader02.eternal-september.org comp.lang.ada:54149 Date: 2018-08-12T03:18:29-07:00 List-Id: On Sunday, August 12, 2018 at 5:33:35 PM UTC+10, Simon Wright wrote: > Roger writes: > > > As it now occurs even with GCC 6.1.0 I'm thinking it most likely has > > to do with recent OSX changes. > > Since it occurs on Debian Stretch, GCC 6.3.0, it can't be just macOS. > > The actual error reported can change with successive compilations > (sometimes it says something like 'undeclared variable ""', seems to > settle on the CE), a surefire symptom of bad memory handling. > > > This problem doesn't occur for compile only. > > It occurs when I Build All from GPS > > The error is a crash in the compiler, doesn't matter how you get there. Actually, my main program crashes in the same place every time, even when I change things. I have some C code in my program, could that be the cause of f bad memory handling? Solving this sort of problem is somewhat outside my scope of expertise so any advice is welcome. The first time I had this problem was with a much shorter test program that I was experimenting with C interfaces suggesting that my C code might be the problem. I'll see if I can investigate that.