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: 
 buffer1.nntp.dca1.giganews.com!border1.nntp.dca1.giganews.com!border2.nntp.dca1.giganews.com!nntp.giganews.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!fx01.iad.POSTED!not-for-mail
From: Brad Moore <brad.moore@shaw.ca>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: GNAT stuck, any idea on how to diagnose it?
References: <slrnm1anga.nrc.lithiumcat@nat.rebma.instinctive.eu>
 <vlxfpcmsetjg$.1em03ijtae3i6$.dlg@40tude.net>
In-Reply-To: <vlxfpcmsetjg$.1em03ijtae3i6$.dlg@40tude.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Message-ID: <noiRv.148468$Wt5.147264@fx01.iad>
NNTP-Posting-Host: 68.145.219.148
X-Complaints-To: internet.abuse@sjrb.ca
X-Trace: 1410708115 68.145.219.148 (Sun, 14 Sep 2014 15:21:55 UTC)
NNTP-Posting-Date: Sun, 14 Sep 2014 15:21:55 UTC
Date: Sun, 14 Sep 2014 09:21:55 -0600
X-Received-Bytes: 2328
X-Received-Body-CRC: 1980337375
X-Original-Bytes: 2246
Xref: number.nntp.dca.giganews.com comp.lang.ada:189001
Date: 2014-09-14T09:21:55-06:00
List-Id: <comp.lang.ada>

On 2014-09-14 8:49 AM, Dmitry A. Kazakov wrote:
> On Sun, 14 Sep 2014 09:21:18 +0000 (UTC), Natasha Kerensikova wrote:
>
>> Would you know what is this `gnat1`?
>> What part of the build process is it?
>> What is the command above supposed to perform?
>> Is it known to occasionally take a lot of time?
>
> Yes. It may take relatively much time on its own, but from my experience, I
> can tell that GNAT consumes extremely and unreasonably much memory.
>
> At some point it stops compiling under 32-bit systems because there is not
> enough virtual memory.
>
> You could check if your problem is caused by exhaustion of the physical
> memory and turning to the swap. If swap gets involved it will never end.
>

I have on very rare occasion run into a case where the compiler appears 
to be stuck in an endless loop when encountering some illegal code that 
it couldn't handle. (More typically, this would involve a compiler crash 
where at least you get some diagnostic message offering a clue to the 
problem). In my case, I think it had something to do with a name 
resolution problem I think. I found the source of the problem by 
commenting out sections of new code until the
problem went away, then adding back smaller sections until the program 
reappears, until I zeroed in on the problematic code. Once I realized my
mistake, I changed the code to use legal constructs, and the code 
compiled right away.

Brad