Skip to content

Commit 0e418e5

Browse files
j6tgitster
authored andcommitted
t0005: work around strange $? in ksh when program terminated by a signal
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 <[email protected]> Signed-off-by: Junio C Hamano <[email protected]>
1 parent c30e742 commit 0e418e5

File tree

1 file changed

+1
-0
lines changed

1 file changed

+1
-0
lines changed

t/t0005-signals.sh

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ test_expect_success 'sigchain works' '
1313
test-sigchain >actual
1414
case "$?" in
1515
143) true ;; # POSIX w/ SIGTERM=15
16+
271) true ;; # ksh w/ SIGTERM=15
1617
3) true ;; # Windows
1718
*) false ;;
1819
esac &&

0 commit comments

Comments
 (0)