X-Recipient: archive-cygwin@delorie.com X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org From: Uri Simchoni To: "cygwin@cygwin.com" Date: Tue, 29 Dec 2009 01:07:05 -0500 Subject: RE: Cygwin 1.7.1-1 - problem with non-blocking socket IO Message-ID: References: <20091228172405.GB15530@calimero.vinschen.de> In-Reply-To: <20091228172405.GB15530@calimero.vinschen.de> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Thanks for the quick response. Could you post the patch? Uri. -----Original Message----- From: Corinna Vinschen [mailto:corinna-cygwin@cygwin.com]=20 Sent: Monday, December 28, 2009 7:24 PM To: cygwin@cygwin.com Subject: Re: Cygwin 1.7.1-1 - problem with non-blocking socket IO On Dec 28 10:03, Uri Simchoni wrote: > Hi, >=20 > I seem to have a problem with non-blocking writes to TCP sockets and unix= -domain sockets - they block. >=20 > 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. >=20 > With pipe() it works fine. >=20 > 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 --=20 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