Hi Eric,
> waitpid() distinguishes between normal exits > 128 and a
> signal exit, and all existing shells are good about only reporting core
> dumps or other signal exits when waitpid() says the child exits via
> signal. It's just the ambiguity that results when dealing with $? after
> the fact,
On 06/19/2012 04:11 AM, Bruno Haible wrote:
> Exit codes are limited to be < 128. Values between 128 and 255 are reported
> as core dumps by the invoking shell.
Not true. waitpid() distinguishes between normal exits > 128 and a
signal exit, and all existing shells are good about only reporting co
Exit codes are limited to be < 128. Values between 128 and 255 are reported
as core dumps by the invoking shell. To avoid such misinterpretations,
this fix. The problem was introduced on 2011-07-07.
2012-06-19 Bruno Haible
getopt-gnu: Fix exit code overflow in autoconf t
