This is the mail archive of the
mailing list for the Cygwin project.
Re: Fork issues with long command lines and long $PATH
- From: Daniel Colascione <dan dot colascione at gmail dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 01 Apr 2011 06:13:49 -0700
- Subject: Re: Fork issues with long command lines and long $PATH
- References: <4D5BB1F1.firstname.lastname@example.org> <20110217102703.GA30224@calimero.vinschen.de> <4D7A16B4.email@example.com> <20110311152221.GA4645@ednor.casa.cgf.cx>
On 3/11/2011 7:22 AM, Christopher Faylor wrote:
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
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
What about using a large area of BSS as "stack"?
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple