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: Sun, 5 Dec 2004 12:43:36 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: short fread(), but no ferror/feof Message-ID: <20041205174336.GC21703@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sun, Dec 05, 2004 at 05:17:46PM +0100, Peter ?strand wrote: >I've discovered that fread(ptr, size, nitems, stream) sometimes returns a >value less than "nitems", but does not set feof() nor ferror(). As I >understand, this is incorrect: All fread() documentation I've found >confirms this. For example, IEEE Std 1003.1 says: > >"Upon successful completion, fread() shall return the number of elements >successfully read which is less than nitems only if a read error or >end-of-file is encountered." > >I've only noticed the problem when using fread() on a pipe, and when >setting a (another) file descriptor in the same application in >close-on-exec mode. The details are on http://python.org/sf/1071516. I've >been using the latest Cygwin (as of 2004-12-04) on Windows 98. > >To me, this looks like a Cygwin bug. Any ideas? A simple, compilable test case with results shown on both linux and cygwin would prove your theory. 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/