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: Fri, 16 Sep 2005 14:10:37 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Bash login breaks if too many environment variables are set Message-ID: <20050916181037.GA2494@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <67B13185D126644BA1AC929BE1F942AD7A5B4F 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: <67B13185D126644BA1AC929BE1F942AD7A5B4F@dekomplm001.net.plm.eds.com> User-Agent: Mutt/1.5.8i On Fri, Sep 16, 2005 at 08:04:57PM +0200, Hommersom, Fred wrote: >Perhaps I do not understand it. I was talking about invoking cygin >from native. The native environment grows far over 32 k. It just does >not show up in bash. If I can help by testing the new snapshot: please >supply some hints. AFAICT, Eric is getting sidetracked into issues that are not related to your problem. You can help by running the new snapshot under strace, like you did before. cgf >>On the other hand, POSIX would claim that this usage should be failing >>with E2BIG, not EINVAL. So it looks like Windows does have a hard >>limit at total environment > >size of 32k (in spite of their documentation never mentioning it), but >that cygwin could do better at reporting the error when trying to >invoke a native process. -- 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/