Skip to content

Commit

Permalink
t0005: work around strange $? in ksh when program terminated by a signal
Browse files Browse the repository at this point in the history
ksh93 is known to report $? of programs that terminated by a signal as
256 + signal number instead of 128 + signal number like other POSIX
compliant shells (ksh's behavior is still POSIX compliant in this regard).

Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
  • Loading branch information
j6t authored and gitster committed Jul 9, 2010
1 parent c30e742 commit 0e418e5
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions t/t0005-signals.sh
Expand Up @@ -13,6 +13,7 @@ test_expect_success 'sigchain works' '
test-sigchain >actual
case "$?" in
143) true ;; # POSIX w/ SIGTERM=15
271) true ;; # ksh w/ SIGTERM=15
3) true ;; # Windows
*) false ;;
esac &&
Expand Down

0 comments on commit 0e418e5

Please sign in to comment.