Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<011401c2b1e4$67153c60$e185fea9@oemcomputer>
From:	"Sascha Sommer" <saschasommer AT freenet DOT de>
To:	<cygwin AT cygwin DOT com>
Subject:	read() syscall broken on faster cpu?
Date:	Wed, 1 Jan 2003 23:23:24 +0100
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

Hi,
Is it possible, that the read() syscall sometimes doesn't work correctly on
newer cpus?
I have problems to get the cygwin port of mplayer to work on a p3 800
whereas the
same executable works perfect on a p2 350. I found out, that it sometimes
reads one byte less on the p3 than on the p2. Other people get similar
errors on p4 and athlon cpus.
This is reproducable with the -dumpstream option, which reads the file in
2048 byte blocks and writes it into a new one.I use cygwin 1.3.18. Tell me
if you need more info.

S. Sommer


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

- Raw text -