Re: Cygwin 1.7.1-1 - problem with non-blocking socket IO

2010-03-01 Thread dm . n9107
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 lo

Re: Cygwin 1.7.1-1 - problem with non-blocking socket IO

2009-12-29 Thread Corinna Vinschen
On Dec 29 09:30, Corinna Vinschen wrote: > On Dec 29 01:11, Larry Hall (Cygwin) wrote: > > On 12/29/2009 01:07 AM, Uri Simchoni wrote: > > >Thanks for the quick response. Could you post the patch? > > > > See the cygwin-cvs mailing list for applied patches to Cygwin. In this > > case: > >

Re: Cygwin 1.7.1-1 - problem with non-blocking socket IO

2009-12-29 Thread Corinna Vinschen
On Dec 29 01:11, Larry Hall (Cygwin) wrote: > On 12/29/2009 01:07 AM, Uri Simchoni wrote: > >Thanks for the quick response. Could you post the patch? > > See the cygwin-cvs mailing list for applied patches to Cygwin. In this case: > Tonight

Re: Cygwin 1.7.1-1 - problem with non-blocking socket IO

2009-12-28 Thread Larry Hall (Cygwin)
On 12/29/2009 01:07 AM, Uri Simchoni wrote: Thanks for the quick response. Could you post the patch? See the cygwin-cvs mailing list for applied patches to Cygwin. In this case: -- Larry Hall http://www.rfk.

RE: Cygwin 1.7.1-1 - problem with non-blocking socket IO

2009-12-28 Thread Uri Simchoni
Thanks for the quick response. Could you post the patch? Uri. -Original Message- From: Corinna Vinschen [mailto:corinna-cyg...@cygwin.com] 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

Re: Cygwin 1.7.1-1 - problem with non-blocking socket IO

2009-12-28 Thread Corinna Vinschen
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 EWOU