some Win32 exit codes become 0

[Christopher Faylor]

On Tue, Jun 25, 2002 at 03:39:53PM -0700, Ted Romer wrote:
>In cygwin-1.3.11-3, if I invoke a Win32 process that exits with
>negative status (or status >= 256), cygwin converts the status to 0.
>
>Good practice or not, programs often use -1 as an exit status
>indicating failure, so this makes error checking challenging.
>
>Easy to reproduce:
>
>% perl -e 'exit(-1)' % echo $?  0 % jython nosuchscript.py % echo $?  0
>
>The cause is that sigproc.cc:stopped_or_terminated assumes that the
>EXIT_SIGNAL bit in the exit code in fact indicates that the process
>exited due to a signal.  This is true for cygwin processes, but not for
>Win32 processes.

There are some cases where we can't accommodate pure Windows processes.
This is one of them.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/