X-Recipient: archive-cygwin AT delorie DOT com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; q=dns; s=default; b=dE9DhD
	vo5scfDPTEUtcJ4WDmv2pfjUSyu9B38oEu4ptHnCM1xFiZmLm98Kai+7ADO32yDM
	tv77buhOvzvpAhSX/8xlJ3e6jzOX/OAPR0bg0pz0VYtl+hLDJe46xkIXCvjb+zA2
	3liZXV+r8Q5I5p5/1J3ZbmOwWmCyTr+3hwiig=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:message-id:from:reply-to:to:subject
	:references:in-reply-to:content-type; s=default; bh=r/JX4b0h40Nk
	IKP6Ct93MpD3WvI=; b=CFQAWSmsxNAVEB/h9Z4paD0Sv2gcpswzIx+Kaww2zuZx
	gxXrkvLDjx37yeLoe5wM9L6L9OIqlAfaRT+JvyU+3terTPjoG7fwa08Cao3ersud
	JbNVEPb3czrFrKVM+kjRQv96Ki3BroHp0uzfd9GhXpeDlBFJ3CmL9fmd9koji+Q=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-4.3 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2,NORMAL_HTTP_TO_IP,NUMERIC_HTTP_ADDR,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=H*F:D*nl, HX-Languages-Length:1831, UD:cygwin.com, cygwincom
X-HELO: lb1-smtp-cloud7.xs4all.net
Date: Sat, 27 Jul 2019 12:21:47 +0200
Message-ID: <4b59209a91e8384ec000e2724696791c@smtp-cloud7.xs4all.net>
From: Houder <houder AT xs4all DOT nl>
Reply-To: cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
Subject: Re: Regression (last snapshot)
References: <8f6a87faa9c8130241c026889a01d763 AT xs4all DOT nl> <5414d0e1-79d9-cab7-b1bd-4761265bf8bd AT cornell DOT edu> <265a2749-95b6-38aa-a191-7913bfcc98b6 AT cornell DOT edu> <20190722152016 DOT GE21169 AT calimero DOT vinschen DOT de> <20190722155340 DOT GF21169 AT calimero DOT vinschen DOT de> <20190722164509 DOT GG21169 AT calimero DOT vinschen DOT de> <eb8007691b20df0eb8032ca3d2fa445f AT smtp-cloud8 DOT xs4all DOT net> <b3b04db5-7f03-8281-f376-6cd10207ec01 AT cornell DOT edu>
In-Reply-to: <b3b04db5-7f03-8281-f376-6cd10207ec01@cornell.edu>
Content-Type: text/plain; charset=UTF-8; format=fixed
User-Agent: mua.awk 0.99

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