1.0.24.8: fix scav_lose

Used to do one pointer dereferencing too many when printing the
widetag of the lispobj leading to memory faults, ultimately obscuring
the backtrace instead of losing cleanly. Memory faults during gc could
cause all kinds of trouble rendering the backtrace even less
informative.

diff --git a/src/runtime/gc-common.c b/src/runtime/gc-common.c
index fb006cb..0be3fbf 100644 (file)
--- a/src/runtime/gc-common.c
+++ b/src/runtime/gc-common.c
@@ -1885,7 +1885,7 @@ scav_lose(lispobj *where, lispobj object)
 {
     lose("no scavenge function for object 0x%08x (widetag 0x%x)\n",
          (unsigned long)object,
-         widetag_of(*(lispobj*)native_pointer(object)));
+         widetag_of(object));
 
     return 0; /* bogus return value to satisfy static type checking */
 }

diff --git a/version.lisp-expr b/version.lisp-expr
index b1214b4..16f77cb 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.24.7"
+"1.0.24.8"