[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FOR-RELEASE: Windows related bugs

From: dhruva
Subject: Re: FOR-RELEASE: Windows related bugs
Date: Mon, 19 Jun 2006 13:02:32 +0530

I tried both the cases on CVS HEAD version of GNU Emacs built using
MinGW32 on W-XP machine.
I did not experience any problems. For the TCP server case, I used
the "gnuserv" to test. I have been using it ever since I remember and
have never had any problems.

Please let me know if you need any other info that would help in
resolving the problem if any.


On 6/18/06, Kim F. Storm <address@hidden> wrote:

Would someone please look at the following Windows specific problems
which preferably should be solved before the release.

** Markus Gritsch's report about Emacs looping on Windoze with the following
emacs file, and then reduce Emacs frame width to "something quite narrow":
        (setq-default truncate-lines t)
         '(hscroll-margin 20)
         '(hscroll-step 1)

** TCP server processes do not work on Windows.

TCP/IP server processes created with `make-network-process' consume
excesive CPU on some Windows environments.  Usages of 50% and 100%
CPU time have been observed on different Window XP configurations.
Seems to be a problem in sys_select in w32proc.c.

In its current form, it sys_select says the socket is ready, so we
call server_accept_connection which again calls accept() which returns
-1 with errno == WSAEWOULDBLOCK (10035) indicating that there is no
pending connection to accept.

It seems that to fix this, w32 server sockets must use WSAAsyncSelect
+ FD_ACCEPT to request notifications of incoming connections...

Kim F. Storm <address@hidden> http://www.cua.dk

Emacs-devel mailing list

dhruva (dk)
Contents reflect my personal views only!

reply via email to

[Prev in Thread] Current Thread [Next in Thread]