GNAT stuck, any idea on how to diagnose it?

[Natasha Kerensikova <lithiumcat@instinctive.eu>]

Hello,

I have a library project, called Natools, where I accumulate
miscellaneous small stuff. I also have a test suite, and a binary called
`test_all` that runs all the test suites.

Since I'm accumulating stuff, and test_all is accessing everything, it's
getting larger and larger, and takes more and more time to build. So far
so good.

However a few days ago it seems I've reached a threshold where gnatmake
takes a much longer time to finish. I've tried letting it run, and so
far it has taken 41 CPU hours without any sign of progress, while
without my latest package test it doesn't take more than a few wallclock
minutes. Moreover, the memory usage reported by the operating system
hasn't changed between a few minutes after start and now.

Here is the command line, word-wrapped to make it easier to read:

/usr/local/gcc-aux/libexec/gcc/x86_64-aux-freebsd9.2/4.9.0/gnat1 -I
--quiet -dumpbase natools-s_expressions-templates-integers.ads -auxbase
natools-s_expressions-templates-integers -O3 -fstack-check=specific
-gnatez -gnatea -gnatec=/home/nat/code/natools/obj/GNAT-TEMP-000004.TMP
-gnatafnovy -gnateE -gnatwae -gnatA
-gnatem=/home/nat/code/natools/obj/GNAT-TEMP-000005.TMP -gnatez
-mtune=generic -march=x86-64
/home/nat/code/natools/src/natools-s_expressions-templates-integers.ads
-o /tmp//ccd4TDPm.s

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?
Can I consider it eternally stuck, or am I just too impatient?
What kind of tool can I used to help answer those questions?



Thanks in advance for your help,
Natasha