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

[Georg Bauhaus <bauhaus@futureapps.invalid>]

On 14.09.14 11:21, Natasha Kerensikova wrote:

> /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`?

The GNAT User's Guide says this in "3.1 Compiling Programs":

    `gcc' is actually a driver program that looks at the extensions of
the file arguments and loads the appropriate compiler. For example, the
GNU C compiler is `cc1', and the Ada compiler is `gnat1'.

The User's Guide is included with the compiler, in any formats the user
may likely prefer.

> What kind of tool can I used to help answer those questions?

My first attempt would be to obtain access to one of the platforms that
have receive more extensive support for the Ada part of GCC, for example
one of the platforms supported by GPL GNAT, or Debian/GNU. This should
help with excluding issues that may need to be attributed to GNAT on FreeBSD.

Then, also, some OS tracing facility may hint at loops.
Another option is to run the translation process from a debugger.