X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Fdebug.lisp;h=b7709e1fe6e042d7205e83451d72acb0d8ef1a6f;hb=f392742d2781f42b3bb15b637e5008e10fbbe092;hp=f238e3d31c6bffc4ec74c66ba859b96072f5a8f8;hpb=c3887143fdc6da9b63d18ce5cde2a0c037ea3a24;p=sbcl.git

diff --git a/src/code/debug.lisp b/src/code/debug.lisp
index f238e3d..b7709e1 100644
--- a/src/code/debug.lisp
+++ b/src/code/debug.lisp
@@ -648,8 +648,6 @@ reset to ~S."
        ;; and when people redirect *ERROR-OUTPUT*, they could
        ;; reasonably expect to see error messages logged there,
        ;; regardless of what the debugger does afterwards.
-       #!+sb-show (sb!conditions::show-condition *debug-condition*
-						 *error-output*)
        (format *error-output*
 	       "~2&debugger invoked on condition of type ~S:~%  "
 	       (type-of *debug-condition*))
@@ -716,7 +714,7 @@ reset to ~S."
 
 ;;; This calls DEBUG-LOOP, performing some simple initializations
 ;;; before doing so. INVOKE-DEBUGGER calls this to actually get into
-;;; the debugger. SB!CONDITIONS::ERROR-ERROR calls this in emergencies
+;;; the debugger. SB!KERNEL::ERROR-ERROR calls this in emergencies
 ;;; to get into a debug prompt as quickly as possible with as little
 ;;; risk as possible for stepping on whatever is causing recursive
 ;;; errors.