X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com Subject: Re: problems with exit codes on 64-bit Windows XP Pro x64 In-Reply-To: Message from Corinna Vinschen of "Tue, 07 Feb 2006 11:01:35 +0100." <20060207100135.GL15572@calimero.vinschen.de> Date: Tue, 07 Feb 2006 08:10:34 -0800 Message-ID: <16330.1139328634@gemini> From: Kevin Layer X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 Corinna Vinschen wrote: >> On Feb 6 14:49, Kevin Layer wrote: >> > I'm running the latest cygwin (1.5.19, see cygcheck below). >> > >> > My application is a native Windows app (64 and 32-bit). It includes >> > no cygwin libraries and is not compiled with cygwin's gcc. When I >> > execute cygwin programs from my app, however, the return value >> > obtained from cygwin programs is always 0. >> > >> > More precisely, I spawn a particular cygwin program, say `make' or >> > `sh', with CreateProcess(). When the program exits >> > GetExitCodeProcess() always sets the exit status to 0, no matter what >> > the real exit status was. >> >> I just applied a patch which should return the correct error code. Thanks! >> Thanks for the testcase, it's highly appreciated, though... it was >> a lot of code for emulating cmd's "echo %errorlevel%" ;-) Yeah. Originally, we thought it was a Microsoft bug... so we went the extra mile. -- 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/