From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16257 invoked by alias); 30 Apr 2011 00:29:56 -0000 Received: (qmail 16247 invoked by uid 22791); 30 Apr 2011 00:29:55 -0000 X-SWARE-Spam-Status: No, hits=1.2 required=5.0 tests=AWL,BAYES_00,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from bramley.apple.com (HELO mail-out.apple.com) (17.151.62.49) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 30 Apr 2011 00:29:24 +0000 MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; CHARSET=US-ASCII Received: from relay13.apple.com ([17.128.113.29]) by mail-out.apple.com (Oracle Communications Messaging Exchange Server 7u4-20.01 64bit (built Nov 21 2010)) with ESMTPS id <0LKF004HSVREDLE1@mail-out.apple.com> for cygwin@cygwin.com; Fri, 29 Apr 2011 17:29:24 -0700 (PDT) Received: from jdong-mac-tower.apple.com (jdong-mac-tower.apple.com [17.213.40.128]) (using TLS with cipher AES128-SHA (AES128-SHA/128 bits)) (Client did not present a certificate) by relay13.apple.com (Apple SCV relay) with SMTP id F9.0A.29082.4E75BBD4; Fri, 29 Apr 2011 17:29:24 -0700 (PDT) Subject: Re: Cygwin 1.7.x on Windows 7: Exit statuses of Win32 executables are sometimes wrong From: John Dong In-reply-to: Date: Sat, 30 Apr 2011 13:23:00 -0000 Cc: cygwin@cygwin.com Message-id: <9A09C2C2-3688-4840-85D2-B2F18290AE8F@apple.com> References: <0C817B08-1920-43DB-B9A0-26E4B2E362EA@apple.com> To: Edward McGuire 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-04/txt/msg00433.txt.bz2 Hi Edward, Yeah, I forgot to mention that I tried scripting it in a batch file outside cygwin in much the same way as your script, and it ran for a day or two without fail. I can keep that going for longer just in case it fails less frequently, but I don't think it's a Windows / MSVCRT bug. John On Apr 29, 2011, at 2:04 PM, Edward McGuire wrote: > On Fri, Apr 29, 2011 at 13:35, John Dong wrote: >> 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. > Have you tried it with the stock Windows command processor? Something > like this (untested) script? > > @echo off > :redo > rem c:\path\to\exiter.exe 0 > if errorlevel 1 exit /b %errorlevel% > echo %errorlevel% > goto:redo > > -- > 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 > -- 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