Subject: [Fwd: [BUG] BSD libc fseek bug]
To: None <netbsd-bugs@netbsd.org>
From: Pavel Tsekov <ptsekov@syntrex.com>
List: netbsd-bugs
Date: 10/23/2001 19:29:48
This is a multi-part message in MIME format.
--------------20B70DE1ACDA9864F0AF9D14
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

 
--------------20B70DE1ACDA9864F0AF9D14
Content-Type: message/rfc822
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Message-ID: <3BD5A82A.58579996@syntrex.com>
Date: Tue, 23 Oct 2001 19:26:02 +0200
From: Pavel Tsekov <ptsekov@syntrex.com>
MIME-Version: 1.0
To: tech@openbsd.org
CC: freebsd-bugs@openbsd.org, netbsd-bugs@openbsd.org
Subject: [BUG] BSD libc fseek bug 
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Please, take a look at the following two
links describing a problem in newlib's
fseek implementation (this one is actually
BSD derived code). It seems this problem
currently exists in *BSDs too - I
didnt actually have the opportunity to test
it myself, but I've looked at the FreeBSD
and OpenBSD implementations of fseek and
it seems they have the problem too.

The first link contains a description of
the problem and testcase, the second one
contains my observations on the problem:

http://www.cygwin.com/ml/cygwin/2001-10/msg01211.html
http://www.cygwin.com/ml/cygwin/2001-10/msg01298.html

--------------20B70DE1ACDA9864F0AF9D14--