Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Mon, 28 Jul 2003 17:14:49 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: readv - incorrect behavior? Message-ID: <20030728211449.GA9548@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <950B6B3FADEC484C8D0AE17EEE55E1FA2E02F9 AT draco DOT analogic DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <950B6B3FADEC484C8D0AE17EEE55E1FA2E02F9@draco.analogic.com> User-Agent: Mutt/1.4.1i On Mon, Jul 28, 2003 at 04:33:57PM -0400, Hirsch, Matthew wrote: >I've encountered a problem with the readv system call under Cygwin of the >form > > int readv(int fd, const struct iovec *vector, int count); > >It appears that readv is reading past the end of the file described by fd >and instead reading until each buffer in the iovec is filled. This is not >limited to disk files, as I originally came across this problem when reading >from a pty's file descriptor. Yep. It's a bug. I've checked in a fix. It will be in the next snapshot. Thanks for the simple test case. That's always appreciated. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/