X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 22 Aug 2008 19:24:20 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: cygwin 1.7.0-28: Broken pipe signal broken? Message-ID: <20080822232420.GA14913@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <1KV3KS-06K7k00 AT fwd26 DOT aul DOT t-online DOT de> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <48AF26BD.8090201@byu.net> 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: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Fri, Aug 22, 2008 at 02:51:09PM -0600, Eric Blake wrote: >-----BEGIN PGP SIGNED MESSAGE----- >Hash: SHA1 > >According to Christopher Faylor on 8/22/2008 1:22 PM: >> On Fri, Aug 22, 2008 at 08:31:07PM +0200, Christian Franke wrote: >>> ... I could also reproduce this problem. >> >> Unfortunately, I can't. >> >> A simple test cause would be appreciated. > >The parallel make is hit and miss; I've seen make go for quite some time >without failures. I'm also seeing occasional failures with gcc -pipe. >But it looks like I've finally stumbled on a 100% reproducible testcase, >in the m4 testsuite. /home/eblake/m4/build/src/m4 is a self-built m4 from >the latest m4.git; when I replace that string with /bin/m4, I don't see >the failure, so it might be something added in m4.git since m4 1.4.10b >that tickles the behavior; I'm still trying to set up a decent debugging >session to catch that. I'll continue trying to trim it down even further, >hopefully to a simple C program; but in the meantime, here's the testcase: > >$ cat foo.m4 >esyscmd(`echo 1m4exit' | /home/eblake/m4/build/src/m4) sysval >$ /bin/m4 foo.m4 >/home/eblake/m4/build/src/m4: write error >1 1 I don't understand how this is a useful test case. I obviously don't have the /home/eblake/m4/build/src/m4. I looked on sourceware and there is no file there either. Have you tried the latest snapshot? I made a grasp-in-the-dark change there. 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/