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 c...@case.edu http://tiswww.cwru.edu/~chet/
