On Fri, 26 Jul 2019 22:12:43, Ken Brown wrote:
> On 7/22/2019 2:47 PM, Houder wrote:
>> The specific regression as reported, has gone.
>>
>> 64-@@ uname -a
>> CYGWIN_NT-6.1 Seven 3.1.0s(0.339/5/3) 2019-07-22 16:43 x86_64 Cygwin
>> 64-@@ ls -lL <(grep bash .bashrc)
>> pr-------- 1 Henri None 0 Jul 22 20:36 /dev/fd/63
>
> It turns out that this isn't completely fixed, but I only see the problem when
> working under X11, and the error message is different. Here are the complete
> reproduction steps:
>
> 1. Start the X server by using the XWin Server shortcut.
>
> 2. Use the X Applications Menu -> System Tools to start an xterm window.
>
> 3. In that window, execute the above 'ls' command.:
>
> $ ls -lL <(grep bash .bashrc)
> pr-------- 1 kbrown None 0 2019-07-26 17:24 /dev/fd/63
> grep: write error: Broken pipe
>
> This is with the 2019-07-22 snapshot. With the 2019-07-25 snapshot, it's
> better
> but still broken: I have to run the ls command twice to get the error:
>
> $ ls -lL <(grep bash .bashrc)
> pr-------- 1 kbrown None 0 2019-07-26 17:39 /dev/fd/63
>
> $ ls -lL <(grep bash .bashrc)
> pr-------- 1 kbrown None 0 2019-07-26 17:39 /dev/fd/63
> grep: write error: Broken pipe
>
> Here's one more fact, which may or not provide further clues: When I exited
> the
> X server while testing the 2019-07-22 snapshot, there was a /bin/sh process
> still running that I couldn't kill with 'kill -9'. I had to kill it with the
> Task Manager.
>
> Finally, here's an excerpt from the strace output for the failing ls command:
Failing ls? ... uhm, grep complains (as ls did in my case) ...
Over all the behavior has simularity w/ the error reported by David Karr:
https://cygwin.com/ml/cygwin/2019-07/msg00150.html
( Piping input from subprocess loses track of temp file )
Regards,
Henri
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
