X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Fri, 11 Mar 2011 16:20:24 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Fork issues with long command lines and long $PATH Message-ID: <20110311152024.GK7064@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <4D5BB1F1 DOT 1060603 AT smarterphone DOT com> <20110217102703 DOT GA30224 AT calimero DOT vinschen DOT de> <4D7A16B4 DOT 1000802 AT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <4D7A16B4.1000802@gmail.com> User-Agent: Mutt/1.5.21 (2010-09-15) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list 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 process. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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