Date: Fri, 11 Mar 2011 10:22:21 -0500
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Fork issues with long command lines and long $PATH
Message-ID: <20110311152221.GA4645@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <4D5BB1F1.1060603@smarterphone.com> <20110217102703.GA30224@calimero.vinschen.de> <4D7A16B4.1000802@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4D7A16B4.1000802@gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com

On Fri, Mar 11, 2011 at 04:33:56AM -0800, Daniel Colascione wrote:
>On 2/17/11 2:27 AM, Corinna Vinschen wrote:
>> There's no way
>> to start a process and tell the Windows loader where you want the stack.
>
>True, but there's also no requirement to use the stack provided by the
>loader.  Why not always allocate a separate stack and switch to it early
>in initialization?

Taking control of the stack allocation doesn't mean that you will
magically be able to allocate space in the same address range in a
forked process.

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