From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4886 invoked by alias); 25 May 2011 14:16:22 -0000 Received: (qmail 4876 invoked by uid 22791); 25 May 2011 14:16:21 -0000 X-SWARE-Spam-Status: No, hits=-0.8 required=5.0 tests=AWL,BAYES_05,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mail.sidefx.com (HELO mail.sidefx.com) (38.99.137.163) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 25 May 2011 14:16:05 +0000 Message-ID: <4DDD0F23.5000807@sidefx.com> Date: Wed, 25 May 2011 14:16:00 -0000 From: Edward Lam User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Cygwin 1.7.x on Windows 7: Exit statuses of Win32 executables are sometimes wrong References: <0C817B08-1920-43DB-B9A0-26E4B2E362EA@apple.com> In-Reply-To: <0C817B08-1920-43DB-B9A0-26E4B2E362EA@apple.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com X-SW-Source: 2011-05/txt/msg00357.txt.bz2 On 29/04/2011 2:35 PM, John Dong wrote: > Reproducing this seems nondeterministic -- sometimes I can get it to > happen in 5 minutes, other times it takes overnight. I've tried using > a different shell (like dash), but it doesn't make a difference, > leading me to suspect this to be a lower-level issue within the > Cygwin DLL. It also seems to not happen for non-zero exit codes (e.g. > checking that exiter.exe 1 returns 1 always seems to succeed), though > I'm not 100% confident that I've tested this thoroughly enough. > > Again, I've not been able to reproduce this under Windows XP using > any version of Cygwin, but I have been able to reproduce it on both > 32-bit and 64-bit Windows 7. I'm not running anything special on this > machine -- it's a fresh install of Windows 7 Professional, just with > Cygwin installed. FWIW, we've been running into this as well. It appears to NOT be a problem with Cygwin 1.5 on Windows 7. It only started happening on Cygwin 1.7. As a result, we haven't had a reliable Windows 7 build machine for a while now because we use a Cygwin gmake process that compiles with MSVC. -Edward -- 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