Fwd: Sbcl-bugs post from [email protected]

Stas Boukarev <[email protected]> Fri, 13 Feb 2026 18:18:25 +0300
Newsgroups gmane.lisp.steel-bank.devel
Message-ID <CAF63=11WkVGNNeB3_6mHRg0iJPmhoQ0q4j3p6PyqFmoZvpiEJQ@mail.gmail.com>
I might have pressed the wrong button.

---------- Forwarded message ----------
From: "[email protected]" <[email protected]>
To: [email protected]
Cc:
Bcc:
Date: Thu, 12 Feb 2026 20:59:48 -0800
Subject: SBCL 2.6.1 SIGILL during make-target-2 warm init on riscv64/linux/musl
Building SBCL 2.6.1 from source on native riscv64 hardware using ECL
24.5.10 as the cross-compilation host results in a SIGILL (signal 4)
crash during the make-target-2 warm init phase. The cross-compilation
(make-host-1) and genesis complete successfully, and the freshly built
SBCL boots and begins warm compilation, but crashes after compiling
src/code/room.lisp.

Build progression

make-host-1 (cross-compilation via ECL): Completes successfully.
make-host-2 / genesis: Completes successfully. Cold core is generated.
Genesis passes are consistent.
make-target-2(warm init): The freshly built SBCL boots from the cold
core and begins compiling. During warm init, three missing foreign
symbols are reported at startup:

Missing required foreign symbol 'fun_end_breakpoint_trap'Missing
required foreign symbol 'fun_end_breakpoint_end'Missing required
foreign symbol 'fun_end_breakpoint_guts'

Despite these warnings, cold init proceeds and warm compilation
begins. The build successfully compiles many files (including the
disassembler) but crashes immediately after compiling
src/code/room.lisp.

Crash output

; compiling file "src/code/room.lisp" (written 26 JAN 2026 09:10:11 PM):

; wrote /builds/.../obj/from-self/src/code/room.fasl
; compilation finished in 0:00:01.999
CORRUPTION WARNING in SBCL pid 2678 tid 2678:
Signal 4 received (PC: 0x518e6f14)
Exiting.
Error opening /dev/tty: No such device or address
ldb> Welcome to LDB, a low-level debugger for the Lisp runtime environment.
Command exited with non-zero status 1

Signal 4 is SIGILL. The crash PC (0x518e6f14) falls within the dynamic
space (base 0x4F000000), indicating the illegal instruction is in
compiled Lisp code rather than the C runtime.

The full build log is attached, and any suggestions on how to proceed
are sincerely appreciated!

--
Sincerely,
Will Sinatra

Alpine · Lambdacreate · Krei · Tenejo

_______________________________________________
Sbcl-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sbcl-devel
sbcl-rv64.log (text/plain, 252.1 KB) - not displayed