X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Mon, 28 Dec 2009 18:24:05 +0100 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: Cygwin 1.7.1-1 - problem with non-blocking socket IO Message-ID: <20091228172405.GB15530@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Dec 28 10:03, Uri Simchoni wrote: > Hi, > > I seem to have a problem with non-blocking writes to TCP sockets and unix-domain sockets - they block. > > The attached program illustrates it - it creates a socketpair(), sets one end to non-blocking and writes to it - expecting to get an EWOULDBLOCK. On my system it hangs. > > With pipe() it works fine. > > Please advise. First of all, thanks for the testcase! I could reproduce the problem easily and after some serious headscratching it turned out to be a really miserable typo which I just didn't see earlier due to the usage of a C++ parameter default. I've applied a patch in CVS. This will be fixed in 1.7.2. Thanks again, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple