SBCL

  1. Bug #1395910
  2. Comment #4

Comment 4 for bug 1395910

Revision history for this message
Douglas Katzman (dougk) wrote :

I see, typexpand does have a type-declaration on its input, but the 'careful' wrapper won't catch an error of type type-error but will catch (error "whatever"). This seems weird.

Plus I found a more interesting failure mode - somewhere we've got *really* unsafe parsing code:

* (SB-C::CAREFUL-SPECIFIER-TYPE '(cons . 3))
CORRUPTION WARNING in SBCL pid 74962(tid 140735206552336):
Memory fault at 0x7 (pc=0x10005869db, sp=0x11ff5b0)
The integrity of this image is possibly compromised.
Continuing with fingers crossed.