git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] t0005: work around strange $? in ksh when program terminated by a signal

From
Jonathan Nieder <jrnieder@gmail.com>
Date
Jul 9, 2010, 14:39 UTC
Message-ID
<20100709143958.GB1980@burratino>
In-Reply-To
<4C36CA2C.5050305@viscovery.net>
Johannes Sixt wrote:
> ksh 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.)
This patch works for me.
 $ ksh t0005-signals.sh
 *   ok 1: sigchain works
 * passed all 1 test(s)
Thanks for the explanation.
Previous: Jeff KingNext: Brandon Casey
Message 4 of 9 in “t0005 failing with ksh93 on linux”
  1. Jonathan NiederJul 9, 2010
  2. t0005: work around strange $? in ksh when program terminated by a signalJohannes Sixt, Jul 9, 2010
  3. Jeff KingJul 9, 2010
  4. Jonathan NiederJul 9, 2010
  5. Brandon CaseyJul 9, 2010
  6. Ævar Arnfjörð BjarmasonJul 9, 2010
  7. Brandon CaseyJul 9, 2010
  8. t0005: work around strange $? in ksh93 when program terminated by a signalJohannes Sixt, Jul 12, 2010
  9. Junio C HamanoJul 12, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.