Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Tue, 28 Jan 2003 16:33:59 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: bug: select() for sockets returned by accept() returns always ready for write (sel.always_ready 1) Message-ID: <20030128153359.GM2117@cygbert.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <200301280644 DOT h0S6ipG21454 AT hki-web-1 DOT sunpoint DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200301280644.h0S6ipG21454@hki-web-1.sunpoint.net> User-Agent: Mutt/1.4i On Tue, Jan 28, 2003 at 08:44:51AM +0200, Risto Virkkala wrote: > After looking select.cc fhandler.cc fhandler_socket.cc I think that the reason could be that in fhandler_socket::accept the socket is not set to CONNECTED state and in fhandler_socket::select_write sets write_ready if socket is in unconnected state. Thanks for the report. It looks pretty much as if you're right here. I've set the returned file descriptor to connected state. Would you mind to test the next available developers snapshot? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Developer mailto:cygwin AT cygwin DOT com Red Hat, Inc. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/