bug#68708: [PATCH] env,kill: Handle unnamed signals

2024-03-13 Thread Pádraig Brady
On 25/01/2024 19:52, Grisha Levit wrote: On Thu, Jan 25, 2024, 09:50 Pádraig Brady wrote: This mostly looks good, except: - No need to clear the errno before kill(3). - Better to use SIG%d rather than the bare %d for signal _names_, as we already parse this format Makes sense, done below.

bug#68708: [PATCH] env,kill: Handle unnamed signals

2024-01-25 Thread Grisha Levit
> On Thu, Jan 25, 2024, 09:50 Pádraig Brady wrote: > This mostly looks good, except: > > - No need to clear the errno before kill(3). > - Better to use SIG%d rather than the bare %d for signal _names_, as we > already parse this format Makes sense, done below. * src/operand2sig.c

bug#68708: [PATCH] env,kill: Handle unnamed signals

2024-01-25 Thread Pádraig Brady
On 24/01/2024 20:40, Grisha Levit wrote: Android reserves [1] some realtime signals and redefines [2] SIGRTMIN, leaving a gap between the signals that have SIG* constants defined in signal.h and SIGRTMIN. When passed such a signal number, gnulib sig2str returns -1 and leaves its signame

bug#68708: [PATCH] env,kill: Handle unnamed signals

2024-01-24 Thread Grisha Levit
Android reserves [1] some realtime signals and redefines [2] SIGRTMIN, leaving a gap between the signals that have SIG* constants defined in signal.h and SIGRTMIN. When passed such a signal number, gnulib sig2str returns -1 and leaves its signame argument unchanged. The signal listing in env