X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Ftoplevel.lisp;h=5a40e8fd0383cb17b49fa5121cdf1c5c0ec62550;hb=5277a0cbf1a72243cad6808883a4847acefc8e6b;hp=5e1e791934636524400bbc5dcefde52d7dd20046;hpb=d7f6139a91d7d9b0667a597584ae306d958bb2f4;p=sbcl.git diff --git a/src/code/toplevel.lisp b/src/code/toplevel.lisp index 5e1e791..5a40e8f 100644 --- a/src/code/toplevel.lisp +++ b/src/code/toplevel.lisp @@ -15,15 +15,16 @@ (defconstant most-positive-fixnum #.sb!vm:*target-most-positive-fixnum* #!+sb-doc - "The fixnum closest in value to positive infinity.") + "the fixnum closest in value to positive infinity") (defconstant most-negative-fixnum #.sb!vm:*target-most-negative-fixnum* #!+sb-doc - "The fixnum closest in value to negative infinity.") + "the fixnum closest in value to negative infinity") -;;;; magic specials initialized by genesis +;;;; magic specials initialized by GENESIS -#!-gengc +;;; FIXME: The DEFVAR here is redundant with the (DECLAIM (SPECIAL ..)) +;;; of all static symbols in early-impl.lisp. (progn (defvar *current-catch-block*) (defvar *current-unwind-protect-block*) @@ -31,24 +32,16 @@ ;;; specials initialized by !COLD-INIT -;;; FIXME: These could be converted to DEFVARs, and the stuff shared -;;; in both #!+GENGC and #!-GENGC (actually everything in #!+GENGC) -;;; could be made non-conditional. -(declaim - #!-gengc - (special *gc-inhibit* *already-maybe-gcing* - *need-to-collect-garbage* - *gc-notify-stream* - *before-gc-hooks* *after-gc-hooks* - #!+x86 *pseudo-atomic-atomic* - #!+x86 *pseudo-atomic-interrupted* - sb!unix::*interrupts-enabled* - sb!unix::*interrupt-pending* - *type-system-initialized*) - #!+gengc - (special *before-gc-hooks* *after-gc-hooks* - *gc-notify-stream* - *type-system-initialized*)) +;;; FIXME: These could be converted to DEFVARs. +(declaim (special *gc-inhibit* *already-maybe-gcing* + *need-to-collect-garbage* + *gc-notify-stream* + *before-gc-hooks* *after-gc-hooks* + #!+x86 *pseudo-atomic-atomic* + #!+x86 *pseudo-atomic-interrupted* + sb!unix::*interrupts-enabled* + sb!unix::*interrupt-pending* + *type-system-initialized*)) (defvar *cold-init-complete-p*) @@ -73,15 +66,20 @@ ;;;; working with *CURRENT-ERROR-DEPTH* and *MAXIMUM-ERROR-DEPTH* -;;; INFINITE-ERROR-PROTECT is used by ERROR and friends to keep us out of -;;; hyperspace. +;;; INFINITE-ERROR-PROTECT is used by ERROR and friends to keep us out +;;; of hyperspace. (defmacro infinite-error-protect (&rest forms) `(unless (infinite-error-protector) + (/show0 "back from INFINITE-ERROR-PROTECTOR") (let ((*current-error-depth* (1+ *current-error-depth*))) + (/show0 "in INFINITE-ERROR-PROTECT, incremented error depth") + #+sb-show (sb-debug:backtrace) ,@forms))) ;;; a helper function for INFINITE-ERROR-PROTECT (defun infinite-error-protector () + (/show0 "entering INFINITE-ERROR-PROTECTOR, *CURRENT-ERROR-DEPTH*=..") + (/hexstr *current-error-depth*) (cond ((not *cold-init-complete-p*) (%primitive print "Argh! error in cold init, halting") (%primitive sb!c:halt)) @@ -92,6 +90,8 @@ (%primitive print "Argh! corrupted error depth, halting") (%primitive sb!c:halt)) ((> *current-error-depth* *maximum-error-depth*) + (/show0 "*MAXIMUM-ERROR-DEPTH*=..") + (/hexstr *maximum-error-depth*) (/show0 "in INFINITE-ERROR-PROTECTOR, calling ERROR-ERROR") (error-error "Help! " *current-error-depth* @@ -99,6 +99,7 @@ "KERNEL:*MAXIMUM-ERROR-DEPTH* exceeded.") t) (t + (/show0 "returning normally from INFINITE-ERROR-PROTECTOR") nil))) ;;; FIXME: I had a badly broken version of INFINITE-ERROR-PROTECTOR at @@ -155,16 +156,16 @@ (defconstant bytes-per-scrub-unit 2048) +;;; Zero the unused portion of the control stack so that old objects +;;; are not kept alive because of uninitialized stack variables. +;;; +;;; FIXME: Why do we need to do this instead of just letting GC read +;;; the stack pointer and avoid messing with the unused portion of +;;; the control stack? (Is this a multithreading thing where there's +;;; one control stack and stack pointer per thread, and it might not +;;; be easy to tell what a thread's stack pointer value is when +;;; looking in from another thread?) (defun scrub-control-stack () - #!+sb-doc - "Zero the unused portion of the control stack so that old objects are not - kept alive because of uninitialized stack variables." - ;; FIXME: Why do we need to do this instead of just letting GC read - ;; the stack pointer and avoid messing with the unused portion of - ;; the control stack? (Is this a multithreading thing where there's - ;; one control stack and stack pointer per thread, and it might not - ;; be easy to tell what a thread's stack pointer value is when - ;; looking in from another thread?) (declare (optimize (speed 3) (safety 0)) (values (unsigned-byte 20))) ; FIXME: DECLARE VALUES? @@ -179,7 +180,7 @@ (look (sap+ ptr bytes-per-scrub-unit) 0 count)) (t (setf (sap-ref-32 ptr offset) 0) - (scrub ptr (+ offset sb!vm:word-bytes) count)))) + (scrub ptr (+ offset sb!vm:n-word-bytes) count)))) (look (ptr offset count) (declare (type system-area-pointer ptr) (type (unsigned-byte 16) offset) @@ -188,14 +189,14 @@ (cond ((= offset bytes-per-scrub-unit) count) ((zerop (sap-ref-32 ptr offset)) - (look ptr (+ offset sb!vm:word-bytes) count)) + (look ptr (+ offset sb!vm:n-word-bytes) count)) (t - (scrub ptr offset (+ count sb!vm:word-bytes)))))) + (scrub ptr offset (+ count sb!vm:n-word-bytes)))))) (let* ((csp (sap-int (sb!c::control-stack-pointer-sap))) (initial-offset (logand csp (1- bytes-per-scrub-unit)))) (declare (type (unsigned-byte 32) csp)) (scrub (int-sap (- csp initial-offset)) - (* (floor initial-offset sb!vm:word-bytes) sb!vm:word-bytes) + (* (floor initial-offset sb!vm:n-word-bytes) sb!vm:n-word-bytes) 0))) #!+x86 ;; (Stack grows downwards.) @@ -205,13 +206,13 @@ (type (unsigned-byte 16) offset) (type (unsigned-byte 20) count) (values (unsigned-byte 20))) - (let ((loc (int-sap (- (sap-int ptr) (+ offset sb!vm:word-bytes))))) + (let ((loc (int-sap (- (sap-int ptr) (+ offset sb!vm:n-word-bytes))))) (cond ((= offset bytes-per-scrub-unit) (look (int-sap (- (sap-int ptr) bytes-per-scrub-unit)) 0 count)) (t ;; need to fix bug in %SET-STACK-REF (setf (sap-ref-32 loc 0) 0) - (scrub ptr (+ offset sb!vm:word-bytes) count))))) + (scrub ptr (+ offset sb!vm:n-word-bytes) count))))) (look (ptr offset count) (declare (type system-area-pointer ptr) (type (unsigned-byte 16) offset) @@ -221,36 +222,34 @@ (cond ((= offset bytes-per-scrub-unit) count) ((zerop (sb!kernel::get-lisp-obj-address (stack-ref loc 0))) - (look ptr (+ offset sb!vm:word-bytes) count)) + (look ptr (+ offset sb!vm:n-word-bytes) count)) (t - (scrub ptr offset (+ count sb!vm:word-bytes))))))) + (scrub ptr offset (+ count sb!vm:n-word-bytes))))))) (let* ((csp (sap-int (sb!c::control-stack-pointer-sap))) (initial-offset (logand csp (1- bytes-per-scrub-unit)))) (declare (type (unsigned-byte 32) csp)) (scrub (int-sap (+ csp initial-offset)) - (* (floor initial-offset sb!vm:word-bytes) sb!vm:word-bytes) + (* (floor initial-offset sb!vm:n-word-bytes) sb!vm:n-word-bytes) 0)))) ;;;; the default toplevel function -;;; FIXME: Most stuff below here can probably be byte-compiled. - (defvar / nil #!+sb-doc - "a list of all the values returned by the most recent top-level EVAL") + "a list of all the values returned by the most recent top level EVAL") (defvar // nil #!+sb-doc "the previous value of /") (defvar /// nil #!+sb-doc "the previous value of //") -(defvar * nil #!+sb-doc "the value of the most recent top-level EVAL") +(defvar * nil #!+sb-doc "the value of the most recent top level EVAL") (defvar ** nil #!+sb-doc "the previous value of *") (defvar *** nil #!+sb-doc "the previous value of **") -(defvar + nil #!+sb-doc "the value of the most recent top-level READ") +(defvar + nil #!+sb-doc "the value of the most recent top level READ") (defvar ++ nil #!+sb-doc "the previous value of +") (defvar +++ nil #!+sb-doc "the previous value of ++") (defvar - nil #!+sb-doc "the form currently being evaluated") -(defvar *prompt* "* " - #!+sb-doc - "The top-level prompt string. This also may be a function of no arguments - that returns a simple-string.") + +;;; the top level prompt string, or a function of no arguments that +;;; returns a simple-string +(defvar *prompt* "* ") (defun interactive-eval (form) "Evaluate FORM, returning whatever it returns and adjusting ***, **, *, @@ -286,12 +285,10 @@ (finish-output (symbol-value name))) (values)) -;;; the default system top-level function +;;; the default system top level function (defun toplevel-init () (/show0 "entering TOPLEVEL-INIT") - (%primitive print "//entering TOPLEVEL-INIT") ; REMOVEME - (let ((sysinit nil) ; value of --sysinit option (userinit nil) ; value of --userinit option @@ -412,8 +409,6 @@ 'string user-home "/.sbclrc")))) - (/show0 "assigned SYSINIT-TRUENAME and USERINIT-TRUENAME") - ;; We wrap all the pre-REPL user/system customized startup code ;; in a restart. @@ -442,11 +437,14 @@ (eval eval) (flush-standard-output-streams))) (continue () - :report "Continue anyway (skipping to toplevel read/eval/print loop)." - (values)) ; (no-op, just fall through) + :report + "Continue anyway (skipping to toplevel read/eval/print loop)." + (/show0 "CONTINUEing from pre-REPL RESTART-CASE") + (values)) ; (no-op, just fall through) (quit () - :report "Quit SBCL (calling #'QUIT, killing the process)." - (quit)))) + :report "Quit SBCL (calling #'QUIT, killing the process)." + (/show0 "falling through to QUIT from pre-REPL RESTART-CASE") + (quit)))) ;; one more time for good measure, in case we fell out of the ;; RESTART-CASE above before one of the flushes in the ordinary @@ -454,7 +452,9 @@ (flush-standard-output-streams) (/show0 "falling into TOPLEVEL-REPL from TOPLEVEL-INIT") - (toplevel-repl noprint)))) + (toplevel-repl noprint) + ;; (classic CMU CL error message: "You're certainly a clever child.":-) + (critically-unreachable "after TOPLEVEL-REPL")))) ;;; read-eval-print loop for the default system toplevel (defun toplevel-repl (noprint) @@ -462,50 +462,63 @@ (let ((* nil) (** nil) (*** nil) (- nil) (+ nil) (++ nil) (+++ nil) - (/// nil) (// nil) (/ nil) - (eof-marker (cons :eof nil))) + (/// nil) (// nil) (/ nil)) + ;; WITH-SIMPLE-RESTART doesn't actually restart its body as some + ;; (like WHN for an embarrassingly long time ca. 2001-12-07) might + ;; think, but instead drops control back out at the end. So when a + ;; TOPLEVEL or outermost-ABORT restart happens, we need this outer + ;; LOOP wrapper to grab control and start over again. (And it also + ;; wraps CATCH 'TOPLEVEL-CATCHER for similar reasons.) + (loop + (/show0 "about to set up restarts in TOPLEVEL-REPL") + ;; There should only be one TOPLEVEL restart, and it's here, so + ;; restarting at TOPLEVEL always bounces you all the way out here. + (with-simple-restart (toplevel + "Restart at toplevel READ/EVAL/PRINT loop.") + ;; We add a new ABORT restart for every debugger level, so + ;; restarting at ABORT in a nested debugger gets you out to the + ;; innermost enclosing debugger, and only when you're in the + ;; outermost, unnested debugger level does restarting at ABORT + ;; get you out to here. + (with-simple-restart + (abort + "Reduce debugger level (leaving debugger, returning to toplevel).") + (catch 'toplevel-catcher + (sb!unix:unix-sigsetmask 0) ; FIXME: What is this for? + (repl noprint) + (critically-unreachable "after REPL"))))))) + +(defun repl (noprint) + (/show0 "entering REPL") + (let ((eof-marker (cons :eof nil))) (loop - (/show0 "at head of outer LOOP in TOPLEVEL-REPL") - ;; There should only be one TOPLEVEL restart, and it's here, so - ;; restarting at TOPLEVEL always bounces you all the way out here. - (with-simple-restart (toplevel - "Restart at toplevel READ/EVAL/PRINT loop.") - ;; We add a new ABORT restart for every debugger level, so - ;; restarting at ABORT in a nested debugger gets you out to the - ;; innermost enclosing debugger, and only when you're in the - ;; outermost, unnested debugger level does restarting at ABORT - ;; get you out to here. - (with-simple-restart (abort - "Reduce debugger level (leaving debugger).") - (catch 'top-level-catcher - (sb!unix:unix-sigsetmask 0) ; FIXME: What is this for? - (/show0 "about to enter inner LOOP in TOPLEVEL-REPL") - (loop ; FIXME: Do we need this inner LOOP? - ;; FIXME: It seems bad to have GC behavior depend on scrubbing - ;; the control stack before each interactive command. Isn't - ;; there some way we can convince the GC to just ignore - ;; dead areas of the control stack, so that we don't need to - ;; rely on this half-measure? - (scrub-control-stack) - (unless noprint - (fresh-line) - (princ (if (functionp *prompt*) - (funcall *prompt*) - *prompt*)) - (flush-standard-output-streams)) - (let ((form (read *standard-input* nil eof-marker))) - (if (eq form eof-marker) - (quit) - (let ((results - (multiple-value-list (interactive-eval form)))) - (unless noprint - (dolist (result results) - (fresh-line) - (prin1 result))))))))))))) + ;; FIXME: It seems bad to have GC behavior depend on scrubbing the + ;; control stack before each interactive command. Isn't there some + ;; way we can convince the GC to just ignore dead areas of the + ;; control stack, so that we don't need to rely on this + ;; half-measure? + (scrub-control-stack) + (unless noprint + (fresh-line) + (princ (if (functionp *prompt*) + (funcall *prompt*) + *prompt*)) + (flush-standard-output-streams)) + (let ((form (read *standard-input* nil eof-marker))) + (cond ((eq form eof-marker) + (/show0 "doing QUIT for EOF in REPL") + (quit)) + (t + (let ((results (multiple-value-list (interactive-eval form)))) + (unless noprint + (dolist (result results) + (fresh-line) + (prin1 result)))))))))) (defun noprogrammer-debugger-hook-fun (condition old-debugger-hook) (declare (ignore old-debugger-hook)) (flet ((failure-quit (&key recklessly-p) + (/show0 "in FAILURE-QUIT (in noprogrammer debugger hook)") (quit :unix-status 1 :recklessly-p recklessly-p))) ;; This HANDLER-CASE is here mostly to stop output immediately ;; (and fall through to QUIT) when there's an I/O error. Thus, @@ -515,12 +528,14 @@ (handler-case (progn (format *error-output* - "~@~2%" + "~&~@~2%" (type-of condition) condition) ;; Flush *ERROR-OUTPUT* even before the BACKTRACE, so that - ;; even if we hit an error within BACKTRACE we'll at least - ;; have the CONDITION printed out before we die. + ;; even if we hit an error within BACKTRACE (e.g. a bug in + ;; the debugger's own frame-walking code, or a bug in a user + ;; PRINT-OBJECT method) we'll at least have the CONDITION + ;; printed out before we die. (finish-output *error-output*) ;; (Where to truncate the BACKTRACE is of course arbitrary, but ;; it seems as though we should at least truncate it somewhere.)