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/
