Update of /cvsroot/sbcl/sbcl
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv29868
Merge partly-working fix for bug 61
... I think this fixes it on sparc, ppc and maybe mips.
... alpha is broken because it seems that just about every
backtrace has a "bogus stack frame", maybe arising from
the PAL stuff? Dunno.
... x86 is broken because, well, erm, dunno.
RCS file: /cvsroot/sbcl/sbcl/BUGS,v
retrieving revision 1.415
retrieving revision 1.416
diff -u -d -r1.415 -r1.416
--- BUGS 27 Jul 2004 11:16:17 -0000 1.415
+++ BUGS 2 Aug 2004 12:29:29 -0000 1.416
@@ -167,6 +167,12 @@
then requesting a BACKTRACE at the debugger prompt gives no information
about where in the user program the problem occurred.
+ (this is apparently mostly fixed on the SPARC and PPC architectures:
+ while giving the backtrace the system complains about "unknown
+ source location: using block start", but apart from that the
+ backtrace seems reasonable. See tests/debug.impure.lisp for a test
Using the pretty-printer from the command prompt gives funny
results, apparently because the pretty-printer doesn't know
@@ -1581,3 +1587,7 @@
Downing fixed most of the problems on non-x86 architectures, but on
the x86 the backtrace from this evaluation does not reveal anything
about the problem. (See tests in debug.impure.lisp)
+346: alpha backtrace
+ In sbcl-0.8.13, all backtraces from errors caused by internal errors
+ on the alpha seem to have a "bogus stack frame".
RCS file: /cvsroot/sbcl/sbcl/version.lisp-expr,v
retrieving revision 1.1745
retrieving revision 1.1746
diff -u -d -r1.1745 -r1.1746
--- version.lisp-expr 2 Aug 2004 11:42:55 -0000 1.1745
+++ version.lisp-expr 2 Aug 2004 12:29:29 -0000 1.1746
@@ -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".)