1.0.20.18: fix sign confusion in reported memory fault addresses

 * ...the mechanism sucks as much as ever, but at least the reported
   address will make sense for high addresses as well.

diff --git a/src/code/interr.lisp b/src/code/interr.lisp
index 7a48c43..3b75632 100644 (file)
--- a/src/code/interr.lisp
+++ b/src/code/interr.lisp
@@ -495,7 +495,7 @@
   (error 'undefined-alien-function-error))
 
 #!-win32
-(define-alien-variable current-memory-fault-address long)
+(define-alien-variable current-memory-fault-address unsigned-long)
 
 #!-win32
 (defun memory-fault-error ()

diff --git a/version.lisp-expr b/version.lisp-expr
index 74e993f..86d89e6 100644 (file)
--- a/version.lisp-expr
+++ b/version.lisp-expr
@@ -17,4 +17,4 @@
 ;;; 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.20.17"
+"1.0.20.18"