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,FREEMAIL_FROM
	autolearn=unavailable autolearn_force=no version=3.4.4
X-Received: by 10.107.35.200 with SMTP id j191mr13409050ioj.51.1503380627197;
        Mon, 21 Aug 2017 22:43:47 -0700 (PDT)
X-Received: by 10.36.6.7 with SMTP id 7mr507846itv.5.1503380627169; Mon, 21
 Aug 2017 22:43:47 -0700 (PDT)
Path: 
 eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!news.eternal-september.org!feeder.eternal-september.org!aioe.org!news.redatomik.org!feeder.usenetexpress.com!feeder-in1.iad1.usenetexpress.com!border1.nntp.dca1.giganews.com!nntp.giganews.com!x187no259041ite.0!news-out.google.com!c139ni2405itb.0!nntp.google.com!x187no258855ite.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail
Newsgroups: comp.lang.ada
Date: Mon, 21 Aug 2017 22:43:46 -0700 (PDT)
In-Reply-To: <d90e8f5d-90a6-475c-a0af-28d8d10f164f@googlegroups.com>
Complaints-To: groups-abuse@google.com
Injection-Info: glegroupsg2000goo.googlegroups.com;
 posting-host=2601:191:8303:2100:4dbf:79ac:dfdd:9f98;
 posting-account=fdRd8woAAADTIlxCu9FgvDrUK4wPzvy3
NNTP-Posting-Host: 2601:191:8303:2100:4dbf:79ac:dfdd:9f98
References: <d90e8f5d-90a6-475c-a0af-28d8d10f164f@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <1535b1b9-76da-434e-8359-d5671fbe9e48@googlegroups.com>
Subject: Re: Problem with GPS under MacOS
From: Robert Eachus <rieachus@comcast.net>
Injection-Date: Tue, 22 Aug 2017 05:43:47 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Xref: news.eternal-september.org comp.lang.ada:47781
Date: 2017-08-21T22:43:46-07:00
List-Id: <comp.lang.ada>

On Thursday, August 17, 2017 at 4:48:02 PM UTC-4, Laurent wrote:
> Hi
>=20
> I have the problem that when I work with GPS and Gnoga is with'ed that GP=
S 2017 is crashing. In the log I have this:
=20
> Are there other things I could try?

It looks like the problem is a "wild" pointer.  At a guess, it looks like d=
uring finalization a 32-bit value was treated as a 64-bit address. Oops!  I=
'd put a print command in the place where the failure is occurring. I assum=
e you have a minimal program that causes the crash, since it seems to be oc=
curring after the main program completes.