Re: build for i386 broken

[Jasper Taylor]

It still crashes if built with -g, and is possible to get a backtrace 
from gdb, e.g., for the gprolog executable:

Starting program: /home/jaspert/Build/gprolog/src/TopComp/gprolog --version

Program received signal SIGSEGV, Segmentation fault.
0x004af02a in Pl_Unify (start_u_word=2096275536, start_v_word=172431)
    at unify.c:81
81          Bind_UV(u_adr, v_word);
(gdb) bt
#0  0x004af02a in Pl_Unify (start_u_word=2096275536, start_v_word=172431)
    at unify.c:81
#1  0x00449e13 in X1_247465726D5F746F5F676F616C32__a2 ()
#2  0x00015ae3 in ?? ()
#3  0x00000003 in ?? ()
#4  0x0043b420 in X1_2463686F6963655F706F696E745F617267__a3 ()
#5  0x00000000 in ?? ()

On 06/02/2024 13:20, Jasper Taylor wrote:
> I tried to build gprolog for i386 using a debootstrapped Debian 
> release, and found that the resulting executables always crashed 
> immediately. Remembering that I had previously built it successfully I 
> tried earlier git branches, with the same result. I then tried it with 
> earlier versions of the c compiler and libraries, by using earlier 
> Debian versions. Bullseye and Buster also make bad executables, 
> Stretch gives an internal compiler error during build, and Jessie 
> builds and runs OK, even the latest git branch.
>
> That's with the default build settings, I guess the next step is to 
> try on recent distributions again with lower optimization.
>
>     --Jasper