This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: problems with exit codes on 64-bit Windows XP Pro x64


Corinna Vinschen <corinna-cygwin@cygwin.com> 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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]