Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Mon, 10 Sep 2001 18:46:46 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: recv() blocking for non-blocking socket Message-ID: <20010910184646.T937@cygbert.vinschen.de> Mail-Followup-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from omid@acorn-networks.com on Mon, Sep 10, 2001 at 11:38:40AM -0400 On Mon, Sep 10, 2001 at 11:38:40AM -0400, Omid Roshan-Afshar wrote: > I've looked through the archive, and I found > some discussion about using accept() on non-blocking > sockets, but none on recv(). If someone could spot > any stupid errors in the following code, that would > be great. > > { > int true = 1; > if (ioctl(sock_handle, FIONBIO, &true) != 0) { > if (errmsg!=NULL) > sprintf(errmsg, "ioctl(): %s", strerror(errno)); > return GFAPI_ERR_FAIL; > } > } > > I call recv after I do this and it blocks. I *think* I'm > doing the appropriate thing to make the socket non-blocking. Actually that's a bug in Cygwin 1.3.2. It should be solved with the upcoming 1.3.3 version. 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/