This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Fork issues with long command lines and long $PATH
- From: Christopher Faylor <cgf-use-the-mailinglist-please at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 11 Mar 2011 10:22:21 -0500
- Subject: Re: Fork issues with long command lines and long $PATH
- References: <4D5BB1F1.1060603@smarterphone.com> <20110217102703.GA30224@calimero.vinschen.de> <4D7A16B4.1000802@gmail.com>
- Reply-to: cygwin at cygwin dot 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