Perfect hash generator failed

Bug #2055794 reported by Paul F. Dietz
6
This bug affects 1 person
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
                                     { l)
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/>.
   [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::COMPILE-PERFECT-HASH (LAMBDA (#:KEY) ((LAMBDA # # # #) (COND # # #))) #(#\g 5 #\} #\j #\y #\$ ...))
  2: (SB-IMPL::EXPAND-HASH-CASE (((OR # #) 1) ((OR # # # #) 2) ((OR # #) 3) ((OR #) 4) ((OR # # # # #) 5) ((OR #) 6) ...) ((#\g 5) (#\} #\j #\y #\$) (#\- #\|) (#\X) (0 7 4 #\% 3) (#\{) ...) #(1 2 3 4 5 6 ...
  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:SIMPLE-EVAL-IN-LEXENV (CASE 0 ((#\g 5) 1) ((#\} #\j #\y #\$) 2) ((#\- #\|) 3) ((#\X) 4) ...) #<NULL-LEXENV>)
  6: (EVAL (CASE 0 ((#\g 5) 1) ((#\} #\j #\y #\$) 2) ((#\- #\|) 3) ((#\X) 4) ...))
[...]

x86-64, "2.4.2.42-ea5100b9f"

Douglas Katzman (dougk)
Changed in sbcl:
status: New → Fix Committed
Changed in sbcl:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.