X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 16 Nov 2010 16:41:41 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Problem with fork() in latest snapshot Message-ID: <20101116154141.GA32170@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4CDAF5D0 DOT 8080306 AT budcat DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4CDAF5D0.8080306@budcat.com> 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 Nov 10 13:43, Heath Kehoe wrote: > I have ruby 1.9.2 which I built from source. It works fine in cygwin > 1.7.7 and earlier, but in the current snapshot when it does a fork, > the child process dies pretty much instantly. > > I've put together a test case (see attached) which replicates what > ruby is doing so that this problem can be repro'd without needing to > build ruby. It seems that the failure only happens when the fork > call is in a dll, and it also seems to depend on manipulating > threads in close proximity to the fork. > > Here's the test program under 1.7.7: > > $ uname -a > CYGWIN_NT-6.1-WOW64 hkehoe1 1.7.7(0.230/5/3) 2010-08-31 09:58 i686 > Cygwin > $ ./testfork > Before fork > After fork pid=5060 > After fork pid=0 > subprocess status 0 (0x0) > > And here it is in the snapshot: > > $ uname -a > CYGWIN_NT-6.1-WOW64 hkehoe1 1.7.8s(0.233/5/3) 20101102 14:03:08 i686 > Cygwin > $ ./testfork > Before fork > After fork pid=3808 > subprocess status 32512 (0x7f00) > > > Note the missing 'After fork' message from the child and the -127 > exit status. > > An strace of testfork will reveal this error occurring shortly after > the fork returns in the child: > --- Process 2944, exception C0000005 at 610E4B8C > (the process ID is the child's) Would you mind to test which snapshot introduced this problem? Thanks, 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