Re: Bug: full call to SB-BIGNUM:%BIGNUM-LENGTH with high debug
Stas Boukarev <[email protected]>
| Newsgroups | gmane.lisp.steel-bank.devel |
|---|---|
| Message-ID | <CAF63=13JL=7t0FUGSEMYkqhSpMyEWReiQyaqtxRucTaK00LL2A@mail.gmail.com> |
Fixed. Thanks. On Tue, Jan 20, 2026 at 1:12 PM Eric Marsden via Sbcl-devel <[email protected]> wrote: > > Hi, > > From random-integer testing on AMD64. > > * (lisp-implementation-version) > "2.6.0.142-a478642b3" > * (defvar *s1*) > *S1* > * (defun foo (a b) > (declare (type (integer -134659 -2) b)) > (declare (optimize (debug 3))) > (let ((v (cons 0 0))) > (let ((*s1* (unwind-protect > (unwind-protect a (max (cdr v))) > (ldb (byte 16 0) (ash (car v) (min 34 b)))))) > (progv '(*s1*) (list 0 0) 0)))) > > ; in: DEFUN FOO > ; (ASH (CAR V) (MIN 34 B)) > ; > ; caught STYLE-WARNING: > ; Lisp error during constant folding: > ; The value > ; 0 > ; is not of type > ; BIGNUM > ; when binding SB-IMPL::X > > debugger invoked on a SB-INT:BUG in thread > #<THREAD tid=104211 "main thread" RUNNING {1200BE8003}>: > full call to SB-BIGNUM:%BIGNUM-LENGTH > 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/>. > > > _______________________________________________ > Sbcl-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/sbcl-devel _______________________________________________ Sbcl-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sbcl-devel