This is the mail archive of the
mailing list for the Cygwin project.
Re: Fork issues with long command lines and long $PATH
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Fri, 11 Mar 2011 16:20:24 +0100
- 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>
- Reply-to: cygwin at cygwin dot com
On Mar 11 04:33, 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?
That might even work, but this, too, may be spoiled by the Windows
loader if it loads another DLL prior to cygwin.dll, and that other
DLL happens to use the stack area allocated by Cygwin in the parent
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple