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=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
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@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=UTF-8

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