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=UhofOewlrONKkpqPjaljbM4BtJl/7Rk6wxzXthrc3XL1/neZV9u0+
	Ux8uqXG42Zk1Bcp01rFv+LeCLK8m8qmo1QRtrwrvdsRKG3OVvpCgT3bXJpupaYsp
	aHz5UnCczIwRodUIZK9MzcpYE3eER/Wljltz/+7lCxBGPDULnPxtmQ=
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=tzOsNmjXjZIAPnJ9Inuc2S/BeaM=; b=E9hlzNQkJGv326PhGIcZqYFrnHwH
	brJaICIwJc9ROv7zgITdnp9XdFctvuhtEer68ozH+4VWS+wcwaUUiOmQ5vqI6fCR
	BQbDOoLheyaUd1D6JnQpPXGElKOOt/5Pgu4aMG66Q0wb6ImqgAd4eMSMZ2vlJHKH
	4Qt+3NEODxGx778=
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=-1.0 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:	U2FsdGVkX19CC+PotYJOaPLGChw/iQ9H
Date:	Wed, 16 Jul 2014 10:28:12 -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:	<20140716142812.GA2084@ednor.casa.cgf.cx>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20140715222719 DOT GB4648 AT ednor DOT casa DOT cgf DOT cx> <0D835E9B9CD07F40A48423F80D3B5A702E7ECA06 AT USA7109MB022 DOT na DOT xerox DOT net>
MIME-Version:	1.0
In-Reply-To:	<0D835E9B9CD07F40A48423F80D3B5A702E7ECA06@USA7109MB022.na.xerox.net>
User-Agent:	Mutt/1.5.20 (2009-06-14)

On Wed, Jul 16, 2014 at 12:44:25PM +0000, Nellis, Kenneth wrote:
>From: Christopher Faylor
>>On Tue, Jul 15, 2014 at 06:05:27PM -0400, Christopher Faylor wrote:
>>>Yes, I saw that, but I can't duplicate the problem with that command sequence.
>>
>>I took a stab at another change which may ameliorate the problem.  Please try the latest snapshot.
>
>Indeed, with this snapshot I was not able to reproduce the problem. Thank you!
>
>Cygwin64> uname -srvmo
>CYGWIN_NT-6.1 1.7.31s(0.272/5/3) 20140716 11:15:29 x86_64 Cygwin

Good to hear.  Thanks for confirming.

For the curious, I increased the size of the signal pipe buffer.  I
should have done that when I made signal pipes "nowait" to work around
problems with gdb a couple of releases ago.  I also made the signal
sender retry if WriteFile returns success but the number of bytes sent
was not what was requested (since these are message-style pipes the
size should always be either zero or correct).

Increasing the size of the buffer should have been enough to fix the
problem but, when possible, I like to use two forms of protection when I
fix a bug.

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