X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; q=dns; s=default; b=du sW8vmSFk9o7Nwyd4Igf2J+yrFRkS7WYtGMrSjx2Oa0Lgi3MyoFpC3++KZ+ueSabE iFG4MFMU5STzPVoAIwKEI05MFzsaAk3cMw9sqvGtEPeSbvsOWAC10kERxtm/xZ2r LHa4HDwBWejLNys/o84Rc7BAtnxSXC5ml3Cz/fQ1c= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; s=default; bh=Aqq8wEMv 1mkVGKP5Ko04mp9qO2k=; b=miemcTG7cBFBjtx3kG9VEyjoowqRFwxEePF1IedY +oEtckoZI6tKffOeRoOMb4YwBW3ZZZtIHdm/LP82hHc6iMMXfJ+1A3zbZomOLrkD qBa1EyeiUZpIL9kx2mxJCMN+EK7yKYN+ICJpzmVihWR5/Oeonv+QoUn5zMWS4Vge pwU= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 X-Spam-SWARE-Status: No, score=-3.1 required=5.0 tests=AWL,BAYES_00,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE,SPF_PASS autolearn=ham version=3.3.1 MIME-Version: 1.0 X-Received: by 10.180.74.162 with SMTP id u2mr15335558wiv.36.1372332844796; Thu, 27 Jun 2013 04:34:04 -0700 (PDT) In-Reply-To: <20130627112718.GC25217@calimero.vinschen.de> References: <51CC2018 DOT 2010608 AT cs DOT utoronto DOT ca> <20130627112718 DOT GC25217 AT calimero DOT vinschen DOT de> Date: Thu, 27 Jun 2013 13:34:04 +0200 Message-ID: Subject: Re: Failure with fork() From: Arjen Markus To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 According to the original thread it has to do with handling the stack. The small program is meant to show that there is a discrepancy between the way Cygwin handles this versus the way Linux does that - something to do with accessing more memory pages than expected, but this is not an area I am familiar with ;). > It dies after somewhat below 500 forks and I think I found the reason. > Stay tuned. > I will. It would be great if this can be solved. Regards, Arjen -- 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