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=cjtbVeJ+QzpCqMA0QBIkVejrBM7oX324xgYoEHOkS0U3MGHfEiOge
	YwLwDHgRAZ8RvxKM4PDuAIsXPA6tuQqrXyAgwGz5ksXXd+RFkfXfRMhVBVcNPwb/
	IIeIqOTWiZDgPzk3/GcTQbQ6OBQ1EMI+UxkklUmE6WMS+/+ljY6F0s=
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=+u+RnQ3E7jUONneoJuCjAxwlXS8=; b=WrmW3gHS2QW3GQaRGDvWl2kHPtFq
	wQCwnzHuYPl2a3u+srXZQON3+NOtAw36fVMmK+8U/XAihS7RXFVGU/n+bd2N75zw
	zEkQvUQHnvMjAb6kFdR26MXtE9qRf+1u75gZkkUJsvi4eJe2s1v0RuKMpBZMNvsy
	qcQ6MLsKRCU9DyA=
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.3 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2
X-HELO:	mho-01-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/RIhmzJA072PdqckMO+0km
Date:	Tue, 15 Jul 2014 15:51:55 -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:	<20140715195155.GA5180@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<0D835E9B9CD07F40A48423F80D3B5A702E7EA8E1 AT USA7109MB022 DOT na DOT xerox DOT net> <0D835E9B9CD07F40A48423F80D3B5A702E7EC931 AT USA7109MB022 DOT na DOT xerox DOT net>
MIME-Version:	1.0
In-Reply-To:	<0D835E9B9CD07F40A48423F80D3B5A702E7EC931@USA7109MB022.na.xerox.net>
User-Agent:	Mutt/1.5.20 (2009-06-14)

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?

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 -