X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;ds=inline;f=tests%2Fdebug.impure.lisp;h=9c6473dba99ef64fe0d92eff5aca5d5e34115bff;hb=1dc3a468ba32755c51747d6e85ed32d989f2dd49;hp=b9709f2b5cb792e71363592da45ce7172df1d0a8;hpb=a3d22b67c7e0290a7bbd0ab78d55fbba29f1c01c;p=sbcl.git diff --git a/tests/debug.impure.lisp b/tests/debug.impure.lisp index b9709f2..9c6473d 100644 --- a/tests/debug.impure.lisp +++ b/tests/debug.impure.lisp @@ -14,6 +14,11 @@ ;;;; more information. (cl:in-package :cl-user) + +;;; The debugger doesn't have any native knowledge of the interpreter +(when (eq sb-ext:*evaluator-mode* :interpret) + (sb-ext:quit :unix-status 104)) + ;;;; Check that we get debug arglists right. @@ -38,7 +43,13 @@ ;; happen to be the two case that I had my nose rubbed in when ;; debugging a GC problem caused by applying %SIMPLE-FUN-ARGLIST to ;; a closure. -- WHN 2001-06-05) - (t :unknown))) + (t + #+sb-eval + (if (typep fun 'sb-eval::interpreted-function) + (sb-eval::interpreted-function-lambda-list fun) + :unknown) + #-sb-eval + :unknown))) (defun zoop (zeep &key beep) blurp) @@ -148,18 +159,23 @@ ;; bug 353: This test fails at least most of the time for x86/linux ;; ca. 0.8.20.16. -- WHN - (with-test (:name (:undefined-function :bug-356) - :fails-on '(or (and :x86 :linux) :alpha)) + (with-test (:name (:undefined-function :bug-353) + ;; This used to have fewer :fails-on features pre-0.9.16.38, + ;; but it turns out that the bug was just being masked by + ;; the presence of the IR1 stepper instrumentation (and + ;; is thus again failing now that the instrumentation is + ;; no more). + :fails-on '(or :x86 :x86-64 :alpha)) (assert (verify-backtrace (lambda () (test #'not-optimized)) (list *undefined-function-frame* (list '(flet not-optimized)) (list '(flet test) #'not-optimized)))))) -;;; Division by zero was a common error on PPC. It depended on the +;;; Division by zero was a common error on PPC. It depended on the ;;; return function either being before INTEGER-/-INTEGER in memory, -;;; or more than MOST-POSITIVE-FIXNUM bytes ahead. It also depends on -;;; INTEGER-/-INTEGER calling SIGNED-TRUNCATE. I believe Raymond Toy +;;; or more than MOST-POSITIVE-FIXNUM bytes ahead. It also depends on +;;; INTEGER-/-INTEGER calling SIGNED-TRUNCATE. I believe Raymond Toy ;;; says that the Sparc backend (at least for CMUCL) inlines this, so ;;; if SBCL does the same this test is probably not good for the ;;; Sparc.