X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,SPF_HELO_PASS X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: "dm.n9107" Subject: Re: Cygwin 1.7.1-1 - problem with non-blocking socket IO Date: Tue, 2 Mar 2010 07:49:30 +0000 (UTC) Lines: 13 Message-ID: References: <20091228172405 DOT GB15530 AT calimero DOT vinschen DOT de> <4B399DA6 DOT 2070605 AT cygwin DOT com> <20091229083052 DOT GF15530 AT calimero DOT vinschen DOT de> <20091229220608 DOT GA28728 AT calimero DOT vinschen DOT de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: 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 Corinna Vinschen cygwin.com> writes: > > False alarm. The code is already doing the right thing, AFAICS. > This bug is biting me all the time in the current Cygwin release. Could you please consider releasing a 1.7.1-2 with this fix if 1.7.2 is far off in time. Perhaps this bug is causing a lot of unexplained misbehaviors for other people as well. BR, dm.n9107 -- 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