Package: sbcl
Version: 2:2.5.1-1
Severity: important
X-Debbugs-Cc: mrkissin...@gmail.com

When loading log4cl on the current Debian package of SBCL, it failed.

CL-USER> (ql:quickload "log4cl")
To load "log4cl":
  Load 1 ASDF system:
    log4cl
; Loading "log4cl"

; file: 
/home/mrkissinger/quicklisp/dists/quicklisp/software/log4cl-20230618-git/src/property-parser.lisp
; in: DEFMETHOD PARSE-PROPERTY-LINE (PROPERTY-PARSER T T)
;     (LOG4CL-IMPL:LOG-SEXP "changed separator" 
LOG4CL-IMPL::NAME-TOKEN-SEPARATOR)
; 
; caught ERROR:
;   (during macroexpansion of (SB-PCL::%DEFMETHOD-EXPANDER PARSE-PROPERTY-LINE 
...))
;     Unreachable code reached
;   This is probably a bug in SBCL itself. (Alternatively, SBCL might have been
;   corrupted by bad user code, e.g. by an undefined Lisp operation like
;   (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe
;   Lisp code; or there might be a bug in the OS or hardware that SBCL is 
running
;   on.) If it seems to be a bug in SBCL itself, the maintainers would like to 
know
;   about it. Bug reports are welcome on the SBCL mailing lists, which you can 
find
;   at <http://sbcl.sourceforge.net/>.

;     (LOG4CL-IMPL:LOG-SEXP "changed read-case" 
LOG4CL-IMPL::NAME-TOKEN-READ-CASE)
; 
; caught ERROR:
;   (during macroexpansion of (SB-PCL::%DEFMETHOD-EXPANDER PARSE-PROPERTY-LINE 
...))
;     Unreachable code reached
;   This is probably a bug in SBCL itself. (Alternatively, SBCL might have been
;   corrupted by bad user code, e.g. by an undefined Lisp operation like
;   (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe
;   Lisp code; or there might be a bug in the OS or hardware that SBCL is 
running
;   on.) If it seems to be a bug in SBCL itself, the maintainers would like to 
know
;   about it. Bug reports are welcome on the SBCL mailing lists, which you can 
find
;   at <http://sbcl.sourceforge.net/>.

;     (LOG4CL-IMPL:LOG-SEXP "changed separator" 
LOG4CL-IMPL::NAME-TOKEN-SEPARATOR)
; --> LOG4CL-IMPL:LOG-SEXP-WITH-LEVEL 
; ==>
;   (LOG4CL-IMPL:LOG-DEBUG LOG4CL-IMPL::FROM-LOG-EXPR "changed separator"
;                          LOG4CL-IMPL::NAME-TOKEN-SEPARATOR)
; 
; caught ERROR:
;   during macroexpansion of (LOG-DEBUG FROM-LOG-EXPR "changed separator" ...). 
Use
;   *BREAK-ON-SIGNALS* to intercept.
;   
;      Unreachable code reached
;    This is probably a bug in SBCL itself. (Alternatively, SBCL might have been
;    corrupted by bad user code, e.g. by an undefined Lisp operation like
;    (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe
;    Lisp code; or there might be a bug in the OS or hardware that SBCL is 
running
;    on.) If it seems to be a bug in SBCL itself, the maintainers would like to
;    know about it. Bug reports are welcome on the SBCL mailing lists, which you
;    can find at <http://sbcl.sourceforge.net/>.

;     (LOG4CL-IMPL:LOG-SEXP "changed read-case" 
LOG4CL-IMPL::NAME-TOKEN-READ-CASE)
; --> LOG4CL-IMPL:LOG-SEXP-WITH-LEVEL 
; ==>
;   (LOG4CL-IMPL:LOG-DEBUG LOG4CL-IMPL::FROM-LOG-EXPR "changed read-case"
;                          LOG4CL-IMPL::NAME-TOKEN-READ-CASE)
; 
; caught ERROR:
;   during macroexpansion of (LOG-DEBUG FROM-LOG-EXPR "changed read-case" ...). 
Use
;   *BREAK-ON-SIGNALS* to intercept.
;   
;      Unreachable code reached
;    This is probably a bug in SBCL itself. (Alternatively, SBCL might have been
;    corrupted by bad user code, e.g. by an undefined Lisp operation like
;    (FMAKUNBOUND 'COMPILE), or by stray pointers from alien code or from unsafe
;    Lisp code; or there might be a bug in the OS or hardware that SBCL is 
running
;    on.) If it seems to be a bug in SBCL itself, the maintainers would like to
;    know about it. Bug reports are welcome on the SBCL mailing lists, which you
;    can find at <http://sbcl.sourceforge.net/>.
.
; 
; compilation unit aborted
;   caught 1 fatal ERROR condition
;   caught 4 ERROR conditions
; Evaluation aborted on #<UIOP/LISP-BUILD:COMPILE-FILE-ERROR {1006AEB533}>.
CL-USER> 

Downgrade to the older package, it works.

$ sbcl
This is SBCL 2.2.9.debian, 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.

; file: /usr/share/common-lisp/source/cl-asdf/build/asdf.lisp
; in: DEFUN CALL-WITH-OUTPUT
; (WITH-OUTPUT-TO-STRING (STREAM NIL :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)
; (FUNCALL FUNCTION STREAM))
; --> LET
; ==>
; (MAKE-STRING 31 :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)
;
; note: could not stack allocate:
; (WITH-OUTPUT-TO-STRING (STREAM NIL :ELEMENT-TYPE ELEMENT-TYPE)
; (FUNCALL FUNCTION STREAM))

; in: DEFUN SLURP-STREAM-STRING
; (WITH-OUTPUT-TO-STRING
; (UIOP/STREAM::OUTPUT NIL :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)
; (UIOP/STREAM:COPY-STREAM-TO-STREAM UIOP/STREAM::INPUT UIOP/STREAM::OUTPUT
; :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE))
; --> LET
; ==>
; (MAKE-STRING 31 :ELEMENT-TYPE UIOP/STREAM::ELEMENT-TYPE)
;
; note: could not stack allocate:
; (WITH-OUTPUT-TO-STRING (OUTPUT NIL :ELEMENT-TYPE ELEMENT-TYPE)
; (COPY-STREAM-TO-STREAM INPUT OUTPUT :ELEMENT-TYPE ELEMENT-TYPE))
;
; compilation unit finished
; printed 2 notes

; file: /home/mrkissinger/quicklisp/quicklisp/dist.lisp
; in: DEFUN CONFIG-FILE-INITARGS
; (INTERN (FUNCALL QL-DIST::*INITARG-CASE-CONVERTER* STRING) 'KEYWORD)
;
; note: deleting unreachable code
;
; compilation unit finished
; printed 1 note
* (ql:quickload "log4cl")
To load "log4cl":
  Load 1 ASDF system:
    log4cl
; Loading "log4cl"
[package alexandria]..............................
[package alexandria-2]............................
[package global-vars].............................
[package trivial-garbage].........................
[package bordeaux-threads]........................
[package bt2].....................................
[package log4cl.package-setup]....................
[package log4cl-impl].............................
..................................................
[package log]..
("log4cl")
* (quit)
$

I tried to contact SBCL author, report issue here:
https://bugs.launchpad.net/sbcl/+bug/2092451?comments=all
They cannot reproduce the problem.

Then I tried the official package, it works:

mrkissinger@thinkgirl:~/sbcl-2.5.1-x86-64-linux$ ./run-sbcl.sh --load ~/.sbclrc 
This is SBCL 2.5.1, 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.
* (ql:quickload "log4cl")
To load "log4cl":
  Load 2 ASDF systems:
    asdf bordeaux-threads
  Install 1 Quicklisp release:
    log4cl
; Fetching #<URL 
"http://beta.quicklisp.org/archive/log4cl/2023-06-18/log4cl-20230618-git.tgz";>
; 900.75KB
==================================================
922,372 bytes in 3.25 seconds (276.98KB/sec)
; Loading "log4cl"
[package log4cl.package-setup]....................
[package log4cl-impl].............................
..................................................
[package log]..
("log4cl")
* 

So, I think it is a bug in Debian package of SBCL.

-- System Information:
Debian Release: trixie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 
'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 6.13-amd64 (SMP w/8 CPU threads; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages sbcl depends on:
ii  libc6     2.40-7
ii  libzstd1  1.5.6+dfsg-2

Versions of packages sbcl recommends:
ii  systemd  257.3-1

Versions of packages sbcl suggests:
ii  sbcl-doc     2:2.5.1-1
pn  sbcl-source  <none>
ii  slime        2:2.30+dfsg-3

-- no debconf information

Reply via email to