X-Spam-Check-By: sourceware.org Date: Tue, 7 Mar 2006 17:20:08 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Cc: Joe Buehler Subject: Re: Bug: run emacs: fatal error reading the windows environment Message-ID: <20060307162008.GE3184@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com, Joe Buehler References: <87bqwnwk4p DOT fsf AT ghoti DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87bqwnwk4p.fsf@ghoti.com> User-Agent: Mutt/1.4.2i Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk 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 3 11:47, Kirk Hilliard wrote: > Hi All, > > After upgrading cygwin, my emacs shortcut stopped working and I > discovered that ``run emacs'' yielded the error: > > 12 [main] emacs 900 C:\cygwin\bin\emacs.exe: *** fatal error - > internal error reading the windows environment -- > too many environment variables? After some debugging it turns out that emacs messes around with the global environ variable in some non-portable way. This problem didn't show up before, because Cygwin deliberately overwrite the value of environ with NULL on startup. The newer version of Cygwin does not overwrite environ anymore, so the strange setting of environ gets through to Cygwin and results in a crash since environ just points into nirvana or a surrounding area. This should be fixed in emacs. Joe? Still there somewhere? 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/