This is the mail archive of the cygwin-developers@sources.redhat.com 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]

Re: incorrect exit status from cygwin exec to windows process


The process was exec'ed from a cygwin process, not a windows process...

For example, windows lanuched a cygwin process A. The cygwin process A
exec'ed another cygwin process B.  The exec'ed process should "replace" the
original cygwin process A, and process B's return value should be propagated
back to the windows process.

----- Original Message -----
From: "Christopher Faylor" <cgf@redhat.com>
To: <cygwin-developers@cygwin.com>
Sent: Wednesday, February 28, 2001 11:07 AM
Subject: Re: incorrect exit status from cygwin exec to windows process


> On Tue, Feb 27, 2001 at 11:18:10PM -0800, Jason Gouger wrote:
> >There appears to be some error when a cygwin process exec's another
cygwin
> >process, and returns the exit status to a windows process.  The windows
> >process receives a return code of '131072'.  The problem appeared
sometime
> >after the cygwin 1.1.4 release.
>
> This is how cygwin works.  Since there is no such thing as exec in
windows,
> when process a execs process b, process a exits with a special status
> flagging the owner of "process a" that an exec has occurred.
>
> cgf
>



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