I've built cygwin1.dll from the latest CVS and confirmed that the
problem is fixed. Unfortunately, I've just discovered a second problem,
also starting with the 2011-07-21 snapshot, that only shows up when I
try to start emacs under X (with emacs large address aware). What
happens here is that emacs keeps using more and more CPU (as shown by
Windows Task Manager), but the emacs window never opens. To reproduce,
install emacs-X11 and then do the following:
1. $ peflags --bigaddr=1 /usr/bin/emacs-X11.exe
2. Start the X server. (I use the Start Menu shortcut.)
3. Start emacs from an xterm window:
$ emacs -Q&
As a slight variation on this, you can instead start emacs with the -nw
option:
$ emacs -nw -Q
This tells emacs to use the xterm window for display rather than opening
its own window. The result this time is that you can see the emacs
display, but emacs is unresponsive while the CPU usage increases as before.