X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 25 Aug 2008 13:28:32 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.7.0-28: Broken pipe signal broken?
Message-ID: <20080825172832.GB24956@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20080819030025 DOT GA4204 AT ednor DOT casa DOT cgf DOT cx> <20080819032227 DOT GC4204 AT ednor DOT casa DOT cgf DOT cx> <1KVLws-1iowvw0 AT fwd25 DOT aul DOT t-online DOT de> <20080820160746 DOT GB9452 AT ednor DOT casa DOT cgf DOT cx> <48ACD86A DOT 3060102 AT byu DOT net> <48AF05EB DOT 4020100 AT t-online DOT de> <20080822192212 DOT GA13998 AT ednor DOT casa DOT cgf DOT cx> <48AF26BD DOT 8090201 AT byu DOT net> <20080822232420 DOT GA14913 AT ednor DOT casa DOT cgf DOT cx> <loom DOT 20080825T154445-810 AT post DOT gmane DOT org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <loom.20080825T154445-810@post.gmane.org>
User-Agent: Mutt/1.5.16 (2007-06-09)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT 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

On Mon, Aug 25, 2008 at 03:50:17PM +0000, Eric Blake wrote:
>> Have you tried the latest snapshot?  I made a grasp-in-the-dark change
>> there.
>
>Whatever you did made a difference.  Everything I've tried with a self-built 
>cygwin1.dll with your change has worked without issues, where it was previously 
>failing, including my (private) m4 build that was showing the problem every 
>single test run.

Interesting.  I found an, IMO, vague sentence in MSDN which implied that
something I'd done to improve code flow could have been an issue so I
put things back the way they were.  I've now added a comment to prevent
myself from trying to "clean that up" again.

Thanks for sticking with this.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/