Re: syntax errors produced by interaction between process substitution and a SIGCHLD trap

From	Chet Ramey <chet.ramey@case.edu>
Newsgroups	gnu.bash.bug
Subject	Re: syntax errors produced by interaction between process substitution and a SIGCHLD trap
Date	2019-09-19 10:37 -0400
Message-ID	<mailman.535.1568904333.2190.bug-bash@gnu.org> (permalink)
References	<CAC=jSUVMXPSD=oOhi=9ha=4FeUBsbci3SOVPq0VQAFxWXVzBwQ@mail.gmail.com> <84887b03-1923-41f2-baba-09bfd82509f0@case.edu>

Show all headers | View raw

On 7/31/19 2:35 PM, Travis Everett wrote:

> Bash Version: 5.0
> Patch Level: 7
> Release Status: release
> 
> Description:
>        I stumbled into an odd interaction between process substitution and
> a SIGCHLD trap that causes syntax errors in otherwise valid commands.
> 
>        I managed to pare this down to a very minimal reproduction. I also
> included a more realistic command at the end just in case I'm mistaken
> about the minimal reproduction showing exactly the same issue.

Thanks for the report. This will be fixed in the next devel branch push.

> 
>        I see the same behavior in bash 4.4.23(1)-release and do *not* see
> it in the macos system bash 3.2.57(1)-release.

That's the result of implementing the POSIX requirement of parsing the
contents of $(...) command substitutions, which happened between bash-3.2
and bash-4.0.

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 | Unroll thread

Thread

Re: syntax errors produced by interaction between process substitution and a SIGCHLD trap Chet Ramey <chet.ramey@case.edu> - 2019-09-19 10:37 -0400

csiph-web