Re: Build failure on FreeBSD/PowerPC 32-bit

gdb and SBCL don't go well together because SBCL uses SIGTRAP for perfectly
ordinary events in the execution, making it so that you have to step over
them.
In addition, SIGSEGV is due to the fact that ppc64 at the revision you're
building uses mprotect() to detect pages that have or have not been written
by Lisp.  As of January 2022 the ppc64 architecture no longer uses SIGSEGV
for that.  It may be possible to add -DENABLE_PAGE_PROTECTION=0 to your
CFLAGS in the environment, which should disable page protection but I'm not
sure how well it worked back then. The runtime cost is a slight increase in
GC time, which is fine considering that GC is not the issue at hand.  So
under gdb you should see this instead, which I realize is not significantly
more helpful:


(gdb) *run*

Program received signal SIGTRAP, Trace/breakpoint trap.

0x000000100023827c in ?? ()

Missing separate debuginfos, use: debuginfo-install
glibc-2.17-326.el7_9.3.ppc64le

_______________________________________________
Sbcl-help mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sbcl-help