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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com From: Chris Faylor Date: Tue, 6 Jun 2000 19:19:57 -0400 To: cygwin AT sourceware DOT cygnus DOT com Subject: Re: ioctl and FIONREAD? Message-ID: <20000606191957.D30654@cygnus.com> Reply-To: cygwin AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin AT sourceware DOT cygnus DOT com References: <14653 DOT 34541 DOT 555000 DOT 676136 AT gargle DOT gargle DOT HOWL> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <14653.34541.555000.676136@gargle.gargle.HOWL>; from Markus.Hoenicka@uth.tmc.edu on Tue, Jun 06, 2000 at 11:19:09PM +0000 On Tue, Jun 06, 2000 at 11:19:09PM +0000, Markus Hoenicka wrote: >the following code results in an access violation: > > ioctl(fd, FIONREAD, &nread); > >This is still on B20.1. If anyone could assure me that this works on >the latest (or the upcoming) net release, I'd finally have a good >reason to upgrade. I'm not aware of a version of Cygwin where this has ever worked. I.e., % grep FIONREAD *.cc % >If this still doesn't work: Is there a workaround? I just have to >check whether any data are available to read from fd. Since I'm not aware of any universal way to do this using the Win32 API, I don't think a workaround is possible, unless you want to use non-blocking I/O which should work better in the current net releases than in B20.1. cgf -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com