Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Message-ID: <000c01c0a1cf$6b8b5710$7e222293@fision> From: "Jason Gouger" To: References: <000701c0a156$9b80e8f0$250ddb18 AT fision> <20010228140756 DOT K2327 AT redhat DOT com> Subject: Re: incorrect exit status from cygwin exec to windows process Date: Wed, 28 Feb 2001 13:42:59 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 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" To: 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 >