A Debian user reported a bug in SWI-prolog 5.10.4.

He writes:

   * What led up to the situation?
     My package logol fails to build on IA64 and Sparc, some tests are failing
while ok on other archs
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
     I analysed the reason of failing tests and found that a seg fault occurs
during the treatment
   * What was the outcome of this action?
     Basically, I parse a file, extract some chars at a position and do some
treatment. On those archs,
     I end with a segmentation fault always at the same "time". I added some
logs and it appears it occurs when 
     calling a predicate. I added a write as first instruction of the predicate
and it is not executed. Could be a
      memory allocation issue? See sample log below
   * What outcome did you expect instead?
     Treatment should be as on other archs

He also provided a gdb backtrace on ia64:

Program received signal SIGSEGV, Segmentation fault.
0x400000000007ce21 in into_relocation_chain ()
(gdb) backtrace
#0  0x400000000007ce21 in into_relocation_chain ()
#1  0x4000000000088370 in garbageCollect ()
#2  0x400000000008a3a0 in ensureGlobalSpace ()
#3  0x4000000000046170 in PL_next_solution ()
#4  0x4000000000010360 in main ()

The entire bug log is available here:

   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680116