chain kill signals for cleanup functions
If a piece of code wanted to do some cleanup before exiting
(e.g., cleaning up a lockfile or a tempfile), our usual
strategy was to install a signal handler that did something
like this:
do_cleanup(); /* actual work */
signal(signo, SIG_DFL); /* restore previous behavior */
raise(signo); /* deliver signal, killing ourselves */
For a single handler, this works fine. However, if we want
to clean up two _different_ things, we run into a problem.
The most recently installed handler will run, but when it
removes itself as a handler, it doesn't put back the first
handler.
This patch introduces sigchain, a tiny library for handling
a stack of signal handlers. You sigchain_push each handler,
and use sigchain_pop to restore whoever was before you in
the stack.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-22 14:02:35 +08:00
|
|
|
#!/bin/sh
|
|
|
|
|
|
|
|
|
|
test_description='signals work as we expect'
|
|
|
|
|
. ./test-lib.sh
|
|
|
|
|
|
|
|
|
|
cat >expect <<EOF
|
|
|
|
|
three
|
|
|
|
|
two
|
|
|
|
|
one
|
|
|
|
|
EOF
|
|
|
|
|
|
|
|
|
|
test_expect_success 'sigchain works' '
|
|
|
|
|
test-sigchain >actual
|
|
|
|
|
case "$?" in
|
2009-01-30 16:21:01 +08:00
|
|
|
143) true ;; # POSIX w/ SIGTERM=15
|
2010-07-09 15:05:16 +08:00
|
|
|
271) true ;; # ksh w/ SIGTERM=15
|
chain kill signals for cleanup functions
If a piece of code wanted to do some cleanup before exiting
(e.g., cleaning up a lockfile or a tempfile), our usual
strategy was to install a signal handler that did something
like this:
do_cleanup(); /* actual work */
signal(signo, SIG_DFL); /* restore previous behavior */
raise(signo); /* deliver signal, killing ourselves */
For a single handler, this works fine. However, if we want
to clean up two _different_ things, we run into a problem.
The most recently installed handler will run, but when it
removes itself as a handler, it doesn't put back the first
handler.
This patch introduces sigchain, a tiny library for handling
a stack of signal handlers. You sigchain_push each handler,
and use sigchain_pop to restore whoever was before you in
the stack.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-22 14:02:35 +08:00
|
|
|
3) true ;; # Windows
|
|
|
|
|
*) false ;;
|
|
|
|
|
esac &&
|
|
|
|
|
test_cmp expect actual
|
|
|
|
|
'
|
|
|
|
|
|
2013-06-06 14:34:41 +08:00
|
|
|
test_expect_success !MINGW 'signals are propagated using shell convention' '
|
2013-06-02 01:24:41 +08:00
|
|
|
# we use exec here to avoid any sub-shell interpretation
|
|
|
|
|
# of the exit code
|
|
|
|
|
git config alias.sigterm "!exec test-sigchain" &&
|
|
|
|
|
test_expect_code 143 git sigterm
|
|
|
|
|
'
|
|
|
|
|
|
chain kill signals for cleanup functions
If a piece of code wanted to do some cleanup before exiting
(e.g., cleaning up a lockfile or a tempfile), our usual
strategy was to install a signal handler that did something
like this:
do_cleanup(); /* actual work */
signal(signo, SIG_DFL); /* restore previous behavior */
raise(signo); /* deliver signal, killing ourselves */
For a single handler, this works fine. However, if we want
to clean up two _different_ things, we run into a problem.
The most recently installed handler will run, but when it
removes itself as a handler, it doesn't put back the first
handler.
This patch introduces sigchain, a tiny library for handling
a stack of signal handlers. You sigchain_push each handler,
and use sigchain_pop to restore whoever was before you in
the stack.
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-01-22 14:02:35 +08:00
|
|
|
test_done
|
