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:mime-version:date:message-id:subject:from:to
	:content-type; q=dns; s=default; b=muc72FxA1+2SV2x5Hgv5j+982Ii5X
	remOw+1euoUbUHLrKlHioc7UmCyKukH+VYlOszNr9zHoYKP/oRph9IuVHqMjTWIt
	v1kKm30kMbwDoCj3RIPWJCIuusQsXBaOn461k4JgX+DqMLHojx9r51+Qdt4iaol+
	S9n0GZGrLMYNyw=
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:mime-version:date:message-id:subject:from:to
	:content-type; s=default; bh=Ll6cp5O1PSoHq2L6nFy/m2V9JMM=; b=cUg
	qY4s9JoEJBKbMKCPVHA6AFN4+ia1Gdy8dFhu8Y8ctGhZ2FbCly7hwpZfWr2jKtbL
	MAT+emAb+wwER13vVwtSUVSgWVLSE5cLaA0D9K7kTjQaOVb6DWyQslp9jsVyDggt
	FtZlxKThrimEv3ijEP97O3wqgkg59Hf+yLoB+aBw=
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=-2.3 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2
X-HELO:	mail-ob0-f169.google.com
MIME-Version:	1.0
X-Received:	by 10.182.181.74 with SMTP id du10mr38332935obc.52.1405532202627; Wed, 16 Jul 2014 10:36:42 -0700 (PDT)
Date:	Wed, 16 Jul 2014 13:36:42 -0400
Message-ID:	<CAHfZ7XpoHYmNPx3B=e1VjRzx4u5Acyp-P7pd0daWefJgVM3-EQ@mail.gmail.com>
Subject:	Re: pipe handling errors
From:	Ti Strga <wearyofallthiscrap AT gmail DOT com>
To:	cygwin AT cygwin DOT com

Christopher Faylor wrote:
> 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.

I recall someone on a project here doing a bugfix with a commit log like:

    yyyy-mm-dd The Guy's Name <blah AT blah>

    Fix #nnnnn
    foo.cc (func1):  Belt.
    bar.cc (func2):  Suspenders.

Anyhow, I'm looking forward to trying out the fix myself.  We've been
getting those errors here but not nearly as often.

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