full call to SB-C::%INSTANCE-TYPEP in code calling MISMATCH
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
(lambda (p)
(let ((i 0))
(mismatch (progn (incf i) "abcdef")
:key (progn (incf i) #'identity)
:test (progn (incf i) #'equal)
:end1 (progn (incf i) 4)
:end2 (probe-file p)
)))
==>
full call to SB-C::%
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://
[Condition of type SB-INT:BUG]
Restarts:
0: [ABORT] Exit debugger, returning to top level.
Backtrace:
0: (SB-INT:BUG "full call to ~S" SB-C::%
1: (SB-C::
2: (SB-C::
3: (SB-C::
4: (SB-C:IR2-CONVERT #<SB-C:COMPONENT :NAME (LAMBDA (P)) {100B7A6843}>)
5: (SB-C::
Changed in sbcl: | |
status: | Fix Committed → Fix Released |
2b8cffb27152f21 3d872218d154893 167123f2de