x86-64 sbcl crashes reloading swank
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Invalid
|
Undecided
|
Unassigned |
Bug Description
On my 64-bit Intel Ubuntu Linux laptop, if I start Emacs and then run
SBCL with Slime, the following expression when evaluated in the Slime
REPL crashes SBCL:
(swank-
Doing the same thing on my Raspberry PI works fine. I'm pretty sure
that the expression worked about a year ago on 64-bit Intel hardware.
I see the problem with I load an ASDF system that depends on the
swank ASDF system, since swank.asd causes ASDF to execute the above
expression after its code is loaded.
sbcl --version:
SBCL 1.4.1.56-ff7a0f1
uname -a:
Linux chuwi 4.10.0-38-generic #42~16.04.1-Ubuntu SMP Tue Oct 10 16:32:20 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
*features*:
(:ASDF3.3 :ASDF3.2 :ASDF3.1 :ASDF3 :ASDF2 :ASDF :OS-UNIX :NON-BASE-
:64-BIT :64-BIT-REGISTERS :ALIEN-CALLBACKS :ANSI-CL :ASH-RIGHT-VOPS :C-STACK-
:COMMON-LISP :COMPACT-
:ELF :FLOAT-EQL-VOPS :FP-AND-
:IMMOBILE-SPACE :INLINE-CONSTANTS :INTEGER-EQL-VOP :LARGEFILE :LINKAGE-TABLE :LINUX :LITTLE-ENDIAN
:MEMORY-
:OS-PROVIDES-
:OS-PROVIDES-
:RAW-SIGNED-WORD :RELOCATABLE-HEAP :SB-CORE-
:SB-PACKAGE-LOCKS :SB-SIMD-PACK :SB-SOURCE-
:SBCL :STACK-
:STACK-
:UNDEFINED-
The Emacs *inferior-lisp* buffer contains the following at the end:
fatal error encountered in SBCL pid 5629(tid 0x7fffefdaf700):
%PRIMITIVE HALT called; the party is over.
Error opening /dev/tty: No such device or address
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb> fatal error encountered in SBCL pid 5629(tid 0x7ffff446f700):
%PRIMITIVE HALT called; the party is over.
Welcome to LDB, a low-level debugger for the Lisp runtime environment.
ldb>
Can't reproduce. What's the backtrace in LDB?