[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/54743 (sh(1) exits with code 127 by wait after trap)
The following reply was made to PR bin/54743; it has been noted by GNATS.
From: Robert Elz <kre%munnari.OZ.AU@localhost>
Subject: Re: bin/54743 (sh(1) exits with code 127 by wait after trap)
Date: Sun, 08 Dec 2019 11:49:16 +0700
Date: Sun, 8 Dec 2019 02:10:01 +0000 (UTC)
From: iquiw <iku.iwasa%gmail.com@localhost>
| And it expects exit code provided by "exit" in "trap".
| That is, exit code 0 if "sleep" is killed by "USR1" signal. And exit
| code 1 if "sleep" is killed by "USR2" signal.
Actually it isn't the sleep that receives one of those signals
(which would be difficult to arrange, as the outside world doesn't
know the pid of that sleep process) but the shell that is running
But that's just a quibble - I know what is meant there, and that
isn't working properly either. This one is a new (different) bug...
I'll fix this one as well.
We really need some (real) sh tests for the trap builtin which would
help find some of these issues earlier. One day...
Main Index |
Thread Index |