On Tue, Jun 06, 2006 at 08:33:54PM -0400, Kirk Hilliard wrote: >Hi All, > >On 03 March I pointed out a bug that caused ``run emacs'' to fail with > > 12 [main] emacs 900 C:\cygwin\bin\emacs.exe: *** fatal error - > internal error reading the windows environment -- > too many environment variables? > >The response was promising: > >Corinna Vinschen wrote: >> 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? > >And: > >Alexander Gottwald responded: >> On Fri, 3 Mar 2006, Corinna Vinschen wrote: >> >> > Alexander, does the latest "run" version have the stuff added to >> > regenerate the Windows environment before calling CreateProcess, >> > like cygstart has? >> >> No, sorry. I totally forgot this. I'll create new packages soon > >The bug with ``run emacs'' still seems to be present. What is the >status of this, and is there a bug tracking mechanism that I should be >following other than this list?
What do you glean from http://cygwin.com/problems.html? Does it mention a bug tracking mechanism? Also, do you notice a new cygwin release after 3 Mar 2006? In general, the cygwin web site is apt to have mechanisms for answering questions like these. You might want to try a cygwin snapshot. Snapshots are also mentioned at the main cygwin web page. cgf -- 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/
