Re: [platform-testers] new snapshot available: coreutils-8.24.150-4ab87

[Pádraig Brady]

On 14/01/16 18:33, Pádraig Brady wrote:
> On 14/01/16 17:35, Eric Blake wrote:
>> And then there's ksh, which intentionally sets $? to 256+n rather than
>> 128+n for representing signals, so we absolutely want 'kill -l 257' to
>> report SIGHUP and not that it is out of range for being larger than 255.
> 
> Interesting. I like that one can distinguish signals with this scheme,
> while still having the full 8 bits of exit status available.
> Though it's deviates from common practise and is not compat with
> future wider status values.
> I also see that ksh -l uses this arbitrary value % 256 processing:
> 
>   $ ksh -c 'kill -l $((2**30 + 14))'
>   ALRM

> I'm 50:50 on applying the limit now,
> but have enough info to simplify/fix the test at least.
> 
> thanks a lot for the review/info!

Patch is attached, fixing/simplifying the test,
and adding lots of info about exit status limits.

thanks again,
Pádraig.

kill-large-signals.patch
Description: Text Data