Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 19 Sep 2005 16:29:29 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Bash login breaks if too many environment variables are set Message-ID: <20050919142929.GJ20844@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <67B13185D126644BA1AC929BE1F942AD7A5B56 AT dekomplm001 DOT net DOT plm DOT eds DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <67B13185D126644BA1AC929BE1F942AD7A5B56@dekomplm001.net.plm.eds.com> User-Agent: Mutt/1.4.2i On Sep 16 21:55, Hommersom, Fred wrote: > > >>You can help by running the new snapshot under strace, like you did before. > > I have done three tests: > below the maximum > exactly the maximum > over the maximum Further empirical tests turned out that the environment in Windows NT is not limited, at least not up to a tested size of about 800K. But there is a big problem in Windows nevertheless. When using ASCII functions to access the environment, as Cygwin does, the environment is silently cut off at 32K. There's no error message or any hint in the documentation that something like this would happen when trying to retrieve the environment. Trying to start another process with an ASCII environment > 32K results in an error code returned by CreateProcess. So, for now you have to live with an environment < 32K. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/