X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Wed, 5 Dec 2007 16:32:14 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Odd behaviour of __cygwin_environ? Message-ID: <20071205153214.GI26345@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <042c01c836a1$e6c0d1d0$2e08a8c0 AT CAM DOT ARTIMI DOT COM> <20071205123104 DOT GH26345 AT calimero DOT vinschen DOT de> <04a001c8374f$a58b1a00$2e08a8c0 AT CAM DOT ARTIMI DOT COM> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <04a001c8374f$a58b1a00$2e08a8c0@CAM.ARTIMI.COM> User-Agent: Mutt/1.5.16 (2007-06-09) 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 Dec 5 15:00, Dave Korn wrote: > On 05 December 2007 12:31, Corinna Vinschen wrote: > > Keep in mind that the size of the > > native environment block is restricted to 32K. > > I thought when cygexec was in effect the posix environment and commandline > were passed around-behind-the-back-of CreateProcess, bypassing that limit? Or > does it only handle the commandline but not environment? It also handles the environment block. Is there a native process in the call chain, maybe? If not, I don't see any other chance than to debug this further. spawn_guts() and the build_env() functions might be good starting points for that. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- 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/