compiling float numerical log causes hard crash on WSL

Bug #2076022 reported by Sam Sutcliffe
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Invalid
Undecided
Unassigned

Bug Description

On my WSL install of sbcl compiling a logarithm function where sbcl can deduce that the argument is a single or double float causes a hard crash with no message, however this is NOT the case in slime.
I can still C-c C-c the function in emacs without it crashing sbcl.

It doesn't crash on an available linux machine, however my WSL install is intel CPU and the linux machine is ARM.
Crashing machine: Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz, WSL, windows 10, ubuntu
Non-crashing machine: 2x AMD EPYC 7702, Rocky linux 8

test.lisp:
(defun breaks-things (x)
  (declare (double-float x))
  (log x))

> sbcl --load test.lisp This is SBCL 2.4.7.70-509730034, an implementation of ANSI Common Lisp.
More information about SBCL is available at <http://www.sbcl.org/>.

SBCL is free software, provided as is, with absolutely no warranty.
It is mostly in the public domain; some portions are provided under
BSD-style licenses. See the CREDITS and COPYING files in the
distribution for more information.
! >

Running this with gdb attached says that its a seg-fault:
Program received signal SIGSEGV, Segmentation fault.
0x000000b8006f3341 in ?? ()

Was broken on both SBCL 2.4.6.82-907f5ce03 and SBCL 2.4.7.70-509730034, this seemed to coincide with the various changes to logs in 2.4.2, 2024-02-29.

uname:
Linux DESKTOP-H6JE3F6 4.4.0-19041-Microsoft #4355-Microsoft Thu Apr 12 17:37:00 PST 2024 x86_64 x86_64 x86_64 GNU/Linux

Features:
(:ARENA-ALLOCATOR :X86-64 :GENCGC :64-BIT :ANSI-CL :COMMON-LISP :ELF
 :IEEE-FLOATING-POINT :LINUX :LITTLE-ENDIAN :PACKAGE-LOCAL-NICKNAMES
 :SB-CORE-COMPRESSION :SB-LDB :SB-PACKAGE-LOCKS :SB-THREAD :SB-UNICODE :SBCL
 :UNIX)

Revision history for this message
Stas Boukarev (stassats) wrote :

I would say it's more of a wsl problem, not an sbcl problem.

Changed in sbcl:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.