Date: Tue, 23 Oct 2001 19:29:48 +0200 From: Pavel Tsekov <ptsekov@syntrex.com> To: netbsd-bugs@netbsd.org Cc: freebsd-bugs@freebsd.org Subject: [Fwd: [BUG] BSD libc fseek bug] Message-ID: <3BD5A90C.C310E49A@syntrex.com>
index | next in thread | raw e-mail
[-- Attachment #1 --] [-- Attachment #2 --] X-Mozilla-Status2: 00000000 Message-ID: <3BD5A82A.58579996@syntrex.com> Date: Tue, 23 Oct 2001 19:26:02 +0200 From: Pavel Tsekov <ptsekov@syntrex.com> X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.4.2-2 i686) X-Accept-Language: en 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.htmlhelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3BD5A90C.C310E49A>