Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Date: Mon, 22 Oct 2001 15:06:48 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.3.3-2: fseek fails on multiples of 1024 (binary mode)
Message-ID: <20011022150648.B10383@redhat.com>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20011021225629 DOT 17478 DOT qmail AT foolabs DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20011021225629.17478.qmail@foolabs.com>
User-Agent: Mutt/1.3.21i

On Sun, Oct 21, 2001 at 03:56:29PM -0700, Derek B. Noonburg wrote:
>The fseek function appears to behave strangely when both the offset and
>file size are multiples of 1024.  This is with binary mode files -- I'm
>calling fopen with "rb", and my test file has no control characters (CR,
>LF, ^Z) at all.

This looks like a newlib bug.  I've forwarded this to the newlib mailing
list.

In the meantime if anyone wants to look into the problem, a patch would
be gratefully accepted.

cgf

--
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/