RE: Any way to debug or provide data for problems with Cygwin 1.5.x and XEmacs?
I expect the problems are in cygwin's implementation of select() and more
specifically their handling of /dev/mswindows, which was a special done for
XEmacs. Not sure how you debug it except via code inspection. The symptoms
would be that XEmacs goes catatonic as soons as you fire up anything
requiring select() - e.g. firing up gnus (opens a socket) or starting a
shell window. It used to be that it was required to set CYGWIN=tty in your
environment, but then for a while this wasn't necessary.
andy
-----Original Message-----
From: xemacs-beta-admin(a)xemacs.org
[mailto:xemacs-beta-adminï¼ xemacs.org]On Behalf Of David M. Karr
Sent: Thursday, October 09, 2003 7:14 PM
To: xemacs-beta(a)xemacs.org
Subject: Any way to debug or provide data for problems with Cygwin 1.5.x
and XEmacs?
So it appears that there are major problems with Cygwin 1.5.x and
XEmacs. Is
there anyone who can work with Cygwin people to debug or provide
information
about what might be happening? I've never set up to do any real
debugging of
the XEmacs build, except somewhat at the elisp level. As there's
no practical
way to obtain an "old" version of Cygwin (like 1.3.22, the last
one that worked
for me), I'm pretty much dead in the water until I can get this resolved.
Fortunately, I'm only having this problem on a new box I'm
setting up, and my
other box still has 1.3.22 on it.
--
===================================================================
David M. Karr ; Java/J2EE/XML/Unix/C++
dmkarr(a)earthlink.net ; SCJP; SCWCD; SCBCD