X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=src%2Fcode%2Ftarget-signal.lisp;h=feea1cf7faeb9ccfeda403e324764059d9285b33;hb=c712f88b26cd7547ee984b90e18c134401335bc3;hp=2ae4a88feaf5ce67b33852ad56662debc96f4ee9;hpb=5abf3b4b94c8c2315777e63729293395dc54992c;p=sbcl.git diff --git a/src/code/target-signal.lisp b/src/code/target-signal.lisp index 2ae4a88..feea1cf 100644 --- a/src/code/target-signal.lisp +++ b/src/code/target-signal.lisp @@ -44,23 +44,22 @@ ;; mechanism there are no extra frames on the stack from a ;; previous signal handler when the next signal is delivered ;; provided there is no WITH-INTERRUPTS. - (let ((*unblock-deferrables-on-enabling-interrupts-p* t)) + (let ((*unblock-deferrables-on-enabling-interrupts-p* t) + (sb!debug:*stack-top-hint* (or sb!debug:*stack-top-hint* 'invoke-interruption))) (with-interrupt-bindings - (let ((sb!debug:*stack-top-hint* - (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)))))))))) + (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 @@ -100,6 +99,7 @@ sb!alien:void (where sb!alien:unsigned-long) (old sb!alien:unsigned-long)) +#!-sb-safepoint (sb!alien:define-alien-routine ("unblock_gc_signals" %unblock-gc-signals) sb!alien:void (where sb!alien:unsigned-long) @@ -108,6 +108,7 @@ (defun unblock-deferrable-signals () (%unblock-deferrable-signals 0 0)) +#!-sb-safepoint (defun unblock-gc-signals () (%unblock-gc-signals 0 0)) @@ -190,6 +191,7 @@ (sb!thread:interrupt-thread (sb!thread::foreground-thread) #'interrupt-it))) +#!-sb-wtimer (defun sigalrm-handler (signal info context) (declare (ignore signal info context)) (declare (type system-area-pointer context)) @@ -197,9 +199,9 @@ (defun sigterm-handler (signal code context) (declare (ignore signal code context)) - (sb!thread::terminate-session) - (sb!ext:quit)) + (sb!ext:exit)) +#!-sb-thruption ;;; SIGPIPE is not used in SBCL for its original purpose, instead it's ;;; for signalling a thread that it should look at its interruption ;;; queue. The handler (RUN_INTERRUPTION) just returns if there is @@ -226,11 +228,13 @@ (enable-interrupt sigbus #'sigbus-handler) #!-linux (enable-interrupt sigsys #'sigsys-handler) + #!-sb-wtimer (enable-interrupt sigalrm #'sigalrm-handler) + #!-sb-thruption (enable-interrupt sigpipe #'sigpipe-handler) (enable-interrupt sigchld #'sigchld-handler) #!+hpux (ignore-interrupt sigxcpu) - (unblock-gc-signals) + #!-sb-safepoint (unblock-gc-signals) (unblock-deferrable-signals) (values))