Message-ID: <4F79761E.7030902@peralex.com>
Date: Mon, 02 Apr 2012 11:49:18 +0200
From: Noel Grandin <noel@peralex.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: "cant commit memory for stack" error with perl
References: <4F75A300.4030208@peralex.com> <4F7897C4.1020202@cygwin.com> <4F7961DA.2080203@peralex.com> <20120402085756.GD8014@calimero.vinschen.de>
In-Reply-To: <20120402085756.GD8014@calimero.vinschen.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com


On 2012-04-02 10:57, Corinna Vinschen wrote:
> 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.

Weird, because the script is fairly simple, the includes look like:
use Getopt::Long;
use File::Find;
use File::Basename;
use Archive::Zip qw(:ERROR_CODES :CONSTANTS);

Which I would not have suspected of causing problems. And this worked 
fine for a few months until I updated Cygwin recently.

I think I'll wait until the next Cygwin release comes out, the install 
instructions for the snapshots looks a little hairy.

Thanks for your help.

Disclaimer: http://www.peralex.com/disclaimer.html


--
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