From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11511 invoked by alias); 27 Jul 2019 10:21:54 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 11504 invoked by uid 89); 27 Jul 2019 10:21:53 -0000 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 Received: from lb1-smtp-cloud7.xs4all.net (HELO lb1-smtp-cloud7.xs4all.net) (194.109.24.24) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sat, 27 Jul 2019 10:21:51 +0000 Received: from tmp.Hub8fxJXZU ([83.162.234.136]) by smtp-cloud7.xs4all.net with ESMTPSA id rJpghdqeNur8TrJphh190o; Sat, 27 Jul 2019 12:21:47 +0200 Date: Sat, 27 Jul 2019 10:21:00 -0000 Message-ID: <4b59209a91e8384ec000e2724696791c@smtp-cloud7.xs4all.net> From: Houder Reply-To: cygwin@cygwin.com To: cygwin@cygwin.com Subject: Re: Regression (last snapshot) References: <8f6a87faa9c8130241c026889a01d763@xs4all.nl> <5414d0e1-79d9-cab7-b1bd-4761265bf8bd@cornell.edu> <265a2749-95b6-38aa-a191-7913bfcc98b6@cornell.edu> <20190722152016.GE21169@calimero.vinschen.de> <20190722155340.GF21169@calimero.vinschen.de> <20190722164509.GG21169@calimero.vinschen.de> In-Reply-to: Content-Type: text/plain; charset=UTF-8; format=fixed User-Agent: mua.awk 0.99 X-SW-Source: 2019-07/txt/msg00234.txt.bz2 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