Re: Help: Ada in NetBSD

[Fernando Oleo Blanco <irvise_ml@irvise.xyz>]

Another update on my side, this time with a bit more content.

Following the help provided by Arnaud, I modified the flags with which 
the ACATS's tests get compiled.

To the gnatmake command I added the -f -a -g -j0 flags.

-f to force the recompilation of all files needed with the exception of 
the runtime and library files.
-a is to also force the recompilation of the library & runtime files. 
Whatever is needed.
-g debugging.
-j0 ignored by the ACATS suite provided by Simon (or so says the 
documentation in the shell file).

This flags make the compilation much slower, obviously, since nearly for 
every test the entire Ada library needs to be recompiled. However, this 
started to give me a much better insight on what was going on. Specially 
since now I could debug the failing tests.

I noticed that the first test I started debugging was stuck in a loop 
related to task management. This would explain why I was getting so many 
tests failing with timeouts. Great, but I could only get so much insight.

Arnaud, once again came to the rescue and indicated that I should add 
the -gnata flag.

-gnata is to enable assertions.

And yes, now the tests were finally failing in a meaningful manner. I 
have written the assertions I have found that failed. Remember, I am 
using GCC 10.3 with the patch set that is available in my website. You 
can find it in one of the messages I have sent in this thread.

So, what do we get?

System.Assertions. Assert_Failure in s-tassta.adb:1643 (very common 
everywhere), s-tpopmo.adb:213 (fairly common) and s-taprop.adb:463 
(common in the c9 section).

Storage_Error in s-intman.adb:136

Stack overflow or erroneous memory access in a few tests. I got no 
pointer on where it was happening.

And still some timeouts, but I think they are related to the first 
assertion mentioned.

The "strange" (not that much) is that I have not touched any of these 
files. I will see where they are used in the compiler, how they are used 
and if the issues are related with how NetBSD handles some 
functions/standards... The s-tassta.adb problem I know is 100% related 
to POSIX Threads. Maybe the issue is in the POSIX Threads handling or 
maybe not.


I will keep on digging. Regards,
-- 
Fernando Oleo Blanco
https://irvise.xyz