X-Spam-Check-By: sourceware.org Date: Tue, 7 Feb 2006 11:16:52 +0100 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: problems with exit codes on 64-bit Windows XP Pro x64 Message-ID: <20060207101652.GM15572@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <1649.1139266194@gemini> <20060207100135.GL15572@calimero.vinschen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060207100135.GL15572@calimero.vinschen.de> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com On Feb 7 11:01, 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. Ah, yes, I forgot: Please test the next snapshot from http://cygwin.com/snapshots/ Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/