Failed AVER in SB-C::TRY-PERFECT-FIND/POSITION-MAP on invalid code
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
(lambda (a b)
(cdr a (assoc b '((x) (y) (z)))))
==>
failed AVER:
(EQ
(SB-
SB-C::NODE)
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: [RETRY] Retry SLIME REPL evaluation request.
1: [*ABORT] Return to SLIME's top level.
2: [ABORT] abort thread (#<THREAD tid=1285 "repl-thread" RUNNING {1000FA8003}>)
Backtrace:
0: (SB-C::
1: (SB-C::
2: ((SB-C:DEFTRANSFORM ASSOC) #<SB-C::COMBINATION :FUN #<SB-C::REF :LEAF #<SB-C::GLOBAL-VAR :%SOURCE-NAME ASSOC :TYPE #1=#<SB-
3: (SB-C::
4: (SB-C::IR1-OPTIMIZE #<SB-C:COMPONENT :NAME "<unknown>" {10092C2063}> NIL)
5: (SB-C::
6: (SB-C::
7: (SB-C::IR1-PHASES #<SB-C:COMPONENT :NAME "<unknown>" {10092C2063}>)
8: (SB-C::
9: (SB-C::%COMPILE (LAMBDA (A B) (CDR A (ASSOC B #))) NIL NIL)
[...]
x86-64, "2.4.1.
Changed in sbcl: | |
status: | New → Fix Released |