From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20493 invoked by alias); 28 Jun 2013 10:16:39 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 20456 invoked by uid 89); 28 Jun 2013 10:16:34 -0000 X-Spam-SWARE-Status: No, score=-1.8 required=5.0 tests=AWL,BAYES_00 autolearn=ham version=3.3.1 Received: from aquarius.hirmke.de (HELO calimero.vinschen.de) (217.91.18.234) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 28 Jun 2013 10:16:33 +0000 Received: by calimero.vinschen.de (Postfix, from userid 500) id 559335200D9; Fri, 28 Jun 2013 12:16:30 +0200 (CEST) Date: Fri, 28 Jun 2013 10:20:00 -0000 From: Corinna Vinschen To: cygwin@cygwin.com Subject: Re: Failure with fork() Message-ID: <20130628101630.GS2378@calimero.vinschen.de> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <51CD4177.1040708@gmail.com> <20130628084157.GP2378@calimero.vinschen.de> <00c401ce73e4$d12b80f0$738282d0$@malth.us> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <00c401ce73e4$d12b80f0$738282d0$@malth.us> User-Agent: Mutt/1.5.21 (2010-09-15) X-SW-Source: 2013-06/txt/msg00723.txt.bz2 On Jun 28 02:49, gmt@malth.us wrote: > on Fri, 28 Jun 2013, at 01:41, Corinna Vinschen thusly quipped: > > I think it's a misconception that this very bug is the culprit of > > Cygwin not running under wine. Here's why: > > > > What this bug did was very simple. On each fork, the child process > > committed 4K more stack than its parent. The default stacksize for the > > main thread of a process is 2 Megs. It's a long way for a process to > > take that much space on the stack. So this problem should be visible > > only in rare circumstances wher the main thread of a parent process > > is already filled and then the child crashes because the 2 Megs are > > overrun. As I mentioned in my first post to this thread, the testcase > > took almost 500 forks until the problem occured, 485 to be exact. > > 485*4K = 1.9 Megs. > > > > If anything keeps Cygwin from running under Wine, it's probably some > > different problem, which still need investigating. > > At a glance, http://bugs.winehq.org/show_bug.cgi?id=24018#c9 describes > a seemingly plausible etiology involving the dcrt0.cc code and > differing stack-allocation semantics between wine and windows. That bug in Cygwin is now gone, so we're back to the stack allocation strategy in Wine. Or, it has nothing to do anymore with this issue and it's something completely different. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer 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