* Memory faults signalled differently on Windows -- and not using a
separate condition yet.
(defun undefined-alien-function-error ()
(error 'undefined-alien-function-error))
+#!-win32
(define-alien-variable current-memory-fault-address long)
+#!-win32
(defun memory-fault-error ()
(error 'memory-fault-error
:address current-memory-fault-address))
(cons +exception-stack-overflow+ 'sb!kernel::control-stack-exhausted)
;; Various
(cons-name +exception-single-step+)
- (cons-name +exception-access-violation+)
+ (cons-name +exception-access-violation+) ; FIXME: should turn into MEMORY-FAULT-ERROR
+ ; plus the faulting address
(cons-name +exception-array-bounds-exceeded+)
(cons-name +exception-breakpoint+)
(cons-name +exception-datatype-misalignment+)
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.0.24"
+"1.0.0.25"