X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Wed, 15 Feb 2012 22:35:49 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Snapshot 20120214: fork: can't reserve memory for stack
Message-ID: <20120215213549.GE27454@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <jhh1vj$u77$1 AT dough DOT gmane DOT org> <20120215204723 DOT GC27454 AT calimero DOT vinschen DOT de> <4F3C1D16 DOT 20602 AT redhat DOT com> <20120215211337 DOT GD27454 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <20120215211337.GD27454@calimero.vinschen.de>
User-Agent: Mutt/1.5.21 (2010-09-15)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
List-Id: <cygwin.cygwin.com>
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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 Feb 15 22:13, Corinna Vinschen wrote:
> On Feb 15 14:01, Eric Blake wrote:
> > On 02/15/2012 01:47 PM, Corinna Vinschen wrote:
> > > On Feb 15 11:45, Jehan Bing wrote:
> > >> I'm getting the following error starting with cygwin snapshot
> > >> 20120214 when running a git command:
> > >>
> > >> $ git add bigfile-test.dll
> > >>       0 [main] git 7440 D:\dev_apps\cygwin\bin\git.exe: *** fatal
> > >> error in forked process - fork: can't reserve memory for stack
> > >> 0xAD0000 - 0xBD0000, Win32 error 487
> > > 
> > > I can't reproduce that (also on W7).  How big is bigfile-test.dll?
> > > 
> > > Eric, does git use pthreads and fork from a thread, by any chance?
> > 
> > /me rummages around in git.git
> > 
> > Well, it certainly has both pthread_create and fork calls in the same
> > files (at least run-command.c), although I'm not quire sure if it tries
> > to actually fork from a pthread rather than from the main thread.
> 
> Ok, thanks anyway.  I think I know what happens.  Two days ago I thought
> it is a good idea to use the Windows-provided stack from CreateThread by
> default (== if the application didn't provide its own).  Too bad that
> Windows creates the stacks typically in the lower regions of the
> processes VM.  I guess I have to revert that, so that pthread_create
> always uses a self-created stack again.  Oh well.  So much for "good
> ideas"...

Just reverted in CVS.  Will show up in the next snapshot.


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