X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-1.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org X-Mail-Handler: MailHop Outbound by DynDNS X-Report-Abuse-To: abuse AT dyndns DOT com (see http://www.dyndns.com/services/mailhop/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/E5vJmfI9dLvSY5zUXANwi Date: Mon, 7 May 2012 11:15:42 -0400 From: Christopher Faylor 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: <20120507151542.GA6494@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20120505083518 DOT GA2428 AT calimero DOT vinschen DOT de> <20120506200951 DOT GB11611 AT ednor DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120506200951.GB11611@ednor.casa.cgf.cx> User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , 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 Sun, May 06, 2012 at 04:09:51PM -0400, Christopher Faylor wrote: >On Sun, May 06, 2012 at 10:05:00PM +0200, Rob Burgers wrote: >>Corinna wrote: >>>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. >> >>Okay, may be we should review our starting point. Still one thing >>puzzles me: Despite the fact that no such guarantee can be made, it >>worked fine upto the 1.7.9/1.7.10 kernel releases. If anything can be >>done to 'repair' it, this would be appreciated a lot (even if it were >>done via a registry-key). > >This is probably related to: >http://cygwin.com/ml/cygwin/2012-05/msg00081.html > >It is not likely to change. Actually, I had an idea over the weekend and made some changes to Cygwin's exec handling of non-cygwin applications. So, the latest snapshot should revert this to 1.7.9 behavior. There are still other lurking problems with non-cygwin processes that I need to investigate but that's for after the 1.7.15 release. Please try today's snapshot: http://cygwin.com/snapshots/ -- 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