X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Sat, 5 May 2012 10:35:18 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: 1.7.13/1.7.14: Issue with command prompt not returning when forking process
Message-ID:	<20120505083518.GA2428@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<CA+sc5m=cibkV0bs3ewck97JQRnERkEZCVijWohFQiq0Y979Dog AT mail DOT gmail DOT com> <A1960FFE0F9B444B8512E826965B70763A934CE519 AT ESESSCMS0362 DOT eemea DOT ericsson DOT se>
MIME-Version:	1.0
In-Reply-To:	<A1960FFE0F9B444B8512E826965B70763A934CE519@ESESSCMS0362.eemea.ericsson.se>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On May  5 10:05, Rob Burgers wrote:
> Hi,
> 
> The issue I'm raising in here may be related to this post: http://cygwin.com/ml/cygwin/2012-05/msg00081.html
> It is the first time I read that something may have changed in this area. This is to me unexpected and it caused us quite some debugging to find out as the relation between the updated kernel release due to installation of new packages and the appearance of the issue were not so obvious.
> 
> The example I'm providing in this post is a much simplified version of the actual application. In our application the Launcher (L) process is called from a script and the exit code of the process is needed to determine the next step. Since L never returns until the forked process (S) terminates the exit code will not be available. So running L as a background process doesn't help here.
> 
> I also noticed the difference in behaviour between Cygwin and Linux and since it is Cygwin's intention to provide a Linux look and feel on a Windows environment, I wondering if it is meant to be like this. More over: In the 1.7.10 release the behaviour was still identical to Linux.
> 
> If the statement in the other post remains, I'm wondering whether it would be possible to make the old-behaviour available e.g. by means of a registry key?

If Cygwin behaves different than Linux then that's not really intended.
However, this only goes as far as Cygwin processes are affected.  We
can't (and don't) make any such guarantee for native, non-Cygwin
processes.

Are the affected processes Cygwin processes?  If so, can you please
provide a very simple testcase in plain C?


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -