X-Spam-Check-By: sourceware.org
Message-ID: <fc095b9f0609121028j67029eccn794f71d33e69af91@mail.gmail.com>
Date: Tue, 12 Sep 2006 10:28:05 -0700
From: "Chris McIntosh" <cmcintosh AT gmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Resource Temporarily Unavailble (Message Too Long) Solved
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

First before I get your hopes up. Cygwin maps many errors to EAGAIN
which is outputed as Resource Temporarily Unavailable.

The one I am referring to is win error 234 (ERROR_MORE_DATA)  that
Christopher Faylor recently changed to report error "Message Too
Long".

The root cause was that our environment block was greater than 32K
characters. Some script in our build flow was defining 29000
characters worth of environment variables which made us hit the
Windows ANSI string limit.

Microsoft recommended that we use the unicode CreateProcess and
specify CREATE_UNICIODE_ENVIRONMENT flag, this would allow cygwin not
to hit this 32K limit.

Thought I would put it to the list, to see if anyone has investigated
this, or has any reasons as to why we shouldn't do this.

Thanks,
Chris McIntosh

--
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/