X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
X-Authority-Analysis: v=1.0 c=1 a=KYvE_KlQN7QA:10 a=A9QJJJl43_gA:10  a=xe8BsctaAAAA:8 a=j6825lcPnkotUNiLUVIA:9 a=XhegBt2HeeMR606luz8A:7  a=s2nAb2d7cqv6Bvb1hoR_zgkLxnoA:4 a=eDFNAWYWrCwA:10 a=rPt6xJ-oxjAA:10
Message-ID: <48AF26BD.8090201@byu.net>
Date: Fri, 22 Aug 2008 14:51:09 -0600
From: Eric Blake <ebb9 AT byu DOT net>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.16) Gecko/20080708 Thunderbird/2.0.0.16 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 1.7.0-28: Broken pipe signal broken?
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>
In-Reply-To: <20080822192212.GA13998@ednor.casa.cgf.cx>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes
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

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

The parent process uses popen() to implement esyscmd.  The child m4 was
able to successfully write '1' to stdout (as evidenced by the fact that
the parent process read '1' from the pipe), but then reports a write error
during the atexit() handling.  The expected behavior is to output "1 0",
with no error message.

- --
Don't work too hard, make some time for fun as well!

Eric Blake             ebb9 AT byu DOT net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkivJr0ACgkQ84KuGfSFAYB+NwCgpqDkNKqzK4+9GOTsfdxq3Q5B
KlUAnApFlbv55Ly27lLiXjRBKDhltlPU
=EDtF
-----END PGP SIGNATURE-----

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