Re: [Help-bash] Using lastpipe causes function that takes stdin to fail

[Chet Ramey]

On 11/12/18 10:20 AM, Jesse Hathaway wrote:
> I ran into a strange issue last week when attempting to pipe some
> output into a bash function. The function would always return with an
> error code of 127. I was able to narrow the cause down my use of the
> `lastpipe` option. When I run the below minimal test case without
> `lastpipe`, it completes successfully, but when I use `lastpipe`, the
> function returns an error code of 127. I ran the failing program
> through strace and it appeared the problem might be due to a wait
> system call that doesn't find any matching pids? Any help would be
> greatly appreciated, i'm stumped.

Thanks for the report. This was a bug having to do with the nested
pipelines and lastpipe, fixed back in August as the result of

https://savannah.gnu.org/support/index.php?109541

Chet

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