Perfect hash generator failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
SBCL |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
(case 0
((#\g 5) 1)
((#\} #\j #\y #\$) 2)
((#\- #\|) 3)
((#\X) 4)
((0 7 4 #\% 3) 5)
((#\{) 6)
((#\l) 7)
(t 0))
==>
Perfect hash generator failed on #(g 5 } j y $ - | X 0 7 4 % 3
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=15896 "repl-thread" RUNNING {1000FA8003}>)
Backtrace:
0: (SB-INT:BUG "Perfect hash generator failed on ~X" #(#\g 5 #\} #\j #\y #\$ ...))
1: (SB-C::
2: (SB-IMPL:
3: (MACROEXPAND-1 (CASE 0 ((#\g 5) 1) ((#\} #\j #\y #\$) 2) ((#\- #\|) 3) ((#\X) 4) ...) #<NULL-LEXENV>)
4: (MACROEXPAND (CASE 0 ((#\g 5) 1) ((#\} #\j #\y #\$) 2) ((#\- #\|) 3) ((#\X) 4) ...) #<NULL-LEXENV>)
5: (SB-INT:
6: (EVAL (CASE 0 ((#\g 5) 1) ((#\} #\j #\y #\$) 2) ((#\- #\|) 3) ((#\X) 4) ...))
[...]
x86-64, "2.4.2.
Changed in sbcl: | |
status: | New → Fix Committed |
Changed in sbcl: | |
status: | Fix Committed → Fix Released |