Re: GNAT stuck, any idea on how to diagnose it?

[Natasha Kerensikova <lithiumcat@instinctive.eu>]

Hello,

On 2014-09-14, Dmitry A. Kazakov <mailbox@dmitry-kazakov.de> 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.

As I wrote in the OP, the memory used by gnat1 process, as reported by
the operating system, was constant. Actual numbers depend on what is
measured, as is often the case in modern OS, but all of them where
constant, from 72 MB of physical memory to about 140 MB of addressable
space.

From there, can we deduce that 100% CPU usage with constant memory usage
means the compiler is stuck?

Or are there parts of the compiling process that can legitimately a
significant amount of time without using extra memory?



Thanks for you comments,
Natasha