From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29508 invoked by alias); 28 Jun 2013 09:49:54 -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 29496 invoked by uid 89); 28 Jun 2013 09:49:53 -0000 X-Spam-SWARE-Status: No, score=-2.7 required=5.0 tests=AWL,BAYES_00,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 Received: from mail-pb0-f50.google.com (HELO mail-pb0-f50.google.com) (209.85.160.50) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 28 Jun 2013 09:49:51 +0000 Received: by mail-pb0-f50.google.com with SMTP id wz7so2083250pbc.37 for ; Fri, 28 Jun 2013 02:49:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=from:sender:to:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:content-language:x-gm-message-state; bh=90BytLvLqwMUGABsjzUXhTxXvzppnljdYrzP+7ZsmJY=; b=acbSvPegI8EU1+zgzNf/ZBV9smwwdwkg4qQJ5EhY2lL5yyXO3DsTdWGzhhecydDAKE W5tOh3+iVyOK42KwpcDoK/r41SlPTyT5K18FRXIZVdHa9cURskj4GfmiN9ttISabq1WF SiIOxLFrOhVOw8zZQaUu+BBzYEF0JvhKnViK2gCBe5O4qa82LujeXl2GEAgLTxzVYOtF KIOwzWMhrEbJ1oIEyLdhB7hngodeNiCwEusrgZdu9Fr7xXBAFXaKEDubG1c+i7RkAZU6 Te/niJ+TNcaJ9gfVRZRc6NVyByvAMS3XaJpYkiX0iwTjW3yStUFtAIvuaLVlZ/fS4PtM yAXw== X-Received: by 10.68.255.196 with SMTP id as4mr10493326pbd.54.1372412989888; Fri, 28 Jun 2013 02:49:49 -0700 (PDT) Received: from weaksauce (malth.us. [75.147.143.249]) by mx.google.com with ESMTPSA id ie3sm7380416pbc.13.2013.06.28.02.49.48 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Fri, 28 Jun 2013 02:49:48 -0700 (PDT) From: To: References: <51CD4177.1040708@gmail.com> <20130628084157.GP2378@calimero.vinschen.de> In-Reply-To: <20130628084157.GP2378@calimero.vinschen.de> Subject: RE: Failure with fork() Date: Fri, 28 Jun 2013 10:16:00 -0000 Message-ID: <00c401ce73e4$d12b80f0$738282d0$@malth.us> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmTFMobj5qAAsFHrII2ioroW6MLZHfMIK0YW7hQYWIRlVq4xSqXnKbBFRYHRN8+h+GwyMrh X-SW-Source: 2013-06/txt/msg00722.txt.bz2 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: >=20 > 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 =3D 1.9 Megs. >=20 > 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=3D24018#c9 describes a = seemingly plausible etiology involving the dcrt0.cc code and differing stac= k-allocation semantics between wine and windows. -gmt -- 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