X-Recipient:	archive-cygwin AT delorie DOT com
X-Spam-Check-By:	sourceware.org
Date:	Mon, 2 Apr 2012 10:57:56 +0200
From:	Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: "cant commit memory for stack" error with perl
Message-ID:	<20120402085756.GD8014@calimero.vinschen.de>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<4F75A300 DOT 4030208 AT peralex DOT com> <4F7897C4 DOT 1020202 AT cygwin DOT com> <4F7961DA DOT 2080203 AT peralex DOT com>
MIME-Version:	1.0
In-Reply-To:	<4F7961DA.2080203@peralex.com>
User-Agent:	Mutt/1.5.21 (2010-09-15)
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
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

Please, don't http://cygwin.com/acronyms/#TOFU
Thank you.

On Apr  2 10:22, Noel Grandin wrote:
> Hi
> 
> Thanks for the advise. But I'm still not winning :-(
> 
> I've done a rebaseall and a peflagsall and then a reboot, and I'm
> still seeing the failures.
> 
> Is there anything else I can try, any other debugging I can do?

You could try with the latest developer snapshot from
http://cygwin.com/snapshots/

> >>0 [main] perl 488 child_info_fork::abort: can't commit memory for stack
> >>0x88B000(86016), Win32 error 487
> >>0 [main] perl 3604 child_info_fork::abort: can't commit memory for stack
> >>0x88B000(86016), Win32 error 487

This is strange.  The stack address in question points to a thread
stack.  Trying to create a thread stack in a specific location only
occurs if the process tries to fork() from another thread than the main
thread.  However, if you're running Cygwin 1.7.10 or later, pthread
stacks are not located so low in the memory, since thread stacks are by
default allocated with MEM_TOP_DOWN.

So this looks like perl or the perl package you're using does not use
pthreads, but rather native Windows CreateThread to create a thread.  If
so, it's kind of on its own.


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

- Raw text -