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 14:07:56 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: incorrect exit status from cygwin exec to windows process Message-ID: <20010228140756.K2327@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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <000701c0a156$9b80e8f0$250ddb18@fision>; from cygwin@jason-gouger.com on Tue, Feb 27, 2001 at 11:18:10PM -0800 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