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 Date: Wed, 28 Feb 2001 16:59:25 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: incorrect exit status from cygwin exec to windows process Message-ID: <20010228165925.O2327@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <000701c0a156$9b80e8f0$250ddb18 AT fision> <20010228140756 DOT K2327 AT redhat DOT com> <000c01c0a1cf$6b8b5710$7e222293 AT fision> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <000c01c0a1cf$6b8b5710$7e222293@fision>; from cygwin@jason-gouger.com on Wed, Feb 28, 2001 at 01:42:59PM -0800 On Wed, Feb 28, 2001 at 01:42:59PM -0800, Jason Gouger wrote: >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. I dunno. It may be a bug. Debugging the situation should be pretty simple. cgf