Re: approach to async-signal safety in bash

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: approach to async-signal safety in bash
Date	2020-07-01 15:09 -0400
Organization	ITS, Case Western Reserve University
Message-ID	<mailman.790.1593630550.2574.bug-bash@gnu.org> (permalink)
References	<pn9hipci.dag@gnui.org> <CAB4+JYLs7vO-9dOb9inSRF0QC7d67U9RJnduk3oWy+MiaFUOug@mail.gmail.com> <4e5be040-0d4c-6ccb-efad-5a33352681d3@case.edu> <CAB4+JYKj3=s3Jkjcm9m39JMudEJBO3B8pgb7VFXUQsjwQHS_ig@mail.gmail.com> <d4533231-682d-691a-3e52-df8ce3a0983f@case.edu>

Show all headers | View raw

On 7/1/20 2:18 PM, Godmar Back wrote:

> I did a little experiment, changing find_process to assert that SIGCHLD is
> blocked (like the accompanying comment demands).
> This fails on one of the provided unit tests for me, for instance:

Thanks. I think it's possible for a SIGCHLD to arrive during the window
that find_process is executing when waitchld is not called from a SIGCHLD
signal handler. I'll take a look at fixing that.

Chet

-- 
``The lyf so short, the craft so long to lerne.'' - Chaucer
		 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    chet@case.edu    http://tiswww.cwru.edu/~chet/

Back to gnu.bash.bug | Previous | Next | Find similar

Thread

Re: approach to async-signal safety in bash Chet Ramey <chet.ramey@case.edu> - 2020-07-01 15:09 -0400

csiph-web