X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;ds=sidebyside;f=src%2Fcode%2Ftarget-signal.lisp;h=840604ef78266b1187139ddbbfeaef9b22e30fe3;hb=d833d62dd152879f1aa4e974bd8337c51905d5ba;hp=bea8892e2bd3d08d22819169b5e1fbf02da7e31b;hpb=2bb123efd9f1566b2bff388b55d57698a69b69ba;p=sbcl.git diff --git a/src/code/target-signal.lisp b/src/code/target-signal.lisp index bea8892..840604e 100644 --- a/src/code/target-signal.lisp +++ b/src/code/target-signal.lisp @@ -47,19 +47,20 @@ (let ((*unblock-deferrables-on-enabling-interrupts-p* t)) (with-interrupt-bindings (let ((sb!debug:*stack-top-hint* - (nth-value 1 (sb!kernel:find-interrupted-name-and-frame)))) - (allow-with-interrupts - (nlx-protect (funcall function) - ;; We've been running with deferrables - ;; blocked in Lisp called by a C signal - ;; handler. If we return normally the sigmask - ;; in the interrupted context is restored. - ;; However, if we do an nlx the operating - ;; system will not restore it for us. - (when *unblock-deferrables-on-enabling-interrupts-p* - ;; This means that storms of interrupts - ;; doing an nlx can still run out of stack. - (unblock-deferrable-signals))))))))) + (nth-value 1 (sb!kernel:find-interrupted-name-and-frame)))) + (sb!thread::without-thread-waiting-for (:already-without-interrupts t) + (allow-with-interrupts + (nlx-protect (funcall function) + ;; We've been running with deferrables + ;; blocked in Lisp called by a C signal + ;; handler. If we return normally the sigmask + ;; in the interrupted context is restored. + ;; However, if we do an nlx the operating + ;; system will not restore it for us. + (when *unblock-deferrables-on-enabling-interrupts-p* + ;; This means that storms of interrupts + ;; doing an nlx can still run out of stack. + (unblock-deferrable-signals)))))))))) (defmacro in-interruption ((&key) &body body) #!+sb-doc @@ -196,8 +197,7 @@ (defun sigterm-handler (signal code context) (declare (ignore signal code context)) - (sb!thread::terminate-session) - (sb!ext:quit)) + (sb!ext:exit)) ;;; SIGPIPE is not used in SBCL for its original purpose, instead it's ;;; for signalling a thread that it should look at its interruption