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:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Dgvj3AqvVw4sVLJZD4xgPMwyX22tZoZFypjok5eBl5untClim+gWi
	2qaSt/et8lAmbQhWt70qsRysQrFyrGhFr3ylwHTwqXfVykGT7yCyJ7Db8rdLTYYL
	5043cfK/K35g+gQNVJqhu1EAlaEgJMAxNi9WgAPAHjZf6qCbYZABr8=
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:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; s=default;
	bh=0GXIXbFxBrOK+NmTVVawAlwsuAg=; b=inBYPCdUQJLNWjqOVlbhMS8Mc+OS
	6n0vLCxjA2apLNeyrE820IUTWZQHCklIbckcioj8zngshW6AmgsGxwOlH/XSh8zi
	DZ0gKddstLU4PyNXjtDvPrA9/sQLYw38IgsJEvv5FBbnscGuNLsOLKBcCHYLah6N
	FWU9/4C7mNFLaF8=
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-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-0.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-02-ewr.mailhop.org
X-Mail-Handler:	Dyn Standard SMTP by Dyn
X-Report-Abuse-To:	abuse AT dyndns DOT com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User:	U2FsdGVkX1/1IdDaB0WLMZ0Bahhrt82v
Date:	Tue, 15 Jul 2014 18:05:27 -0400
From:	Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: pipe handling errors
Message-ID:	<20140715220527.GA2607@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20140715195155 DOT GA5180 AT ednor DOT casa DOT cgf DOT cx> <0D835E9B9CD07F40A48423F80D3B5A702E7EC98F AT USA7109MB022 DOT na DOT xerox DOT net>
MIME-Version:	1.0
In-Reply-To:	<0D835E9B9CD07F40A48423F80D3B5A702E7EC98F@USA7109MB022.na.xerox.net>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Tue, Jul 15, 2014 at 08:40:32PM +0000, Nellis, Kenneth wrote:
>From: Christopher Faylor
>>On Tue, Jul 15, 2014 at 07:17:48PM +0000, Nellis, Kenneth wrote:
>>>From: Nellis, Kenneth
>>><snip>
>>>> Well, I'm getting different results with the latest snapshot. 
>>>> Instead of getting the error message, I'm getting a hang for maybe a minute before it continues.
>>>> 
>>>> I used the following command to encourage a failure:
>>>> 
>>>> clear; for f in $(find */Debug -name '*Subsystem'); do echo === $f 
>>>> ===; strings $f | grep '\.cpp$' | sort | uniq -c | sort -n; done
>>><snip>
>>>
>>>Thought it might be useful to add that I can fairly easily get the same 
>>>minute-long hang with a simpler command:
>>>
>>>Cygwin64> strings *Subsystem | wc -l
>>
>>What's your cwd when you run this command?
>
>Well, it *was* on a network drive, but that appears to be irrelevant:
>
>Cygwin64> date; seq 10000 | wc -l; date
>Tue Jul 15 16:31:52 EDT 2014
>10000
>Tue Jul 15 16:32:52 EDT 2014
>Cygwin64> pwd
>/home/knellis
>Cygwin64> cygpath -w $PWD
>C:\cygwin\home\knellis
>Cygwin64> uname -srvmo
>CYGWIN_NT-6.1 1.7.31s(0.273/5/3) 20140715 15:34:37 x86_64 Cygwin
>Cygwin64>

Yes, I saw that, but I can't duplicate the problem with that command sequence.

cgf

--
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

- Raw text -