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
X-Originating-IP: [210.84.179.251]
X-Originating-Email: [jasonwinter AT hotmail DOT com]
X-Sender: jasonwinter AT hotmail DOT com
From: "Jason Winter" <jasonwinter AT hotmail DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: read(): varblk tape records...(& Fix for : read())
Date: Fri, 05 Mar 2004 05:14:13 +0000
Mime-Version: 1.0
Content-Type: text/plain; format=flowed
Message-ID: <Sea2-F42FZEoKz4r02V0005f529@hotmail.com>
X-OriginalArrivalTime: 05 Mar 2004 05:14:14.0157 (UTC) FILETIME=[B3560BD0:01C40270]

Hi Corinna,

It turns out that your new fix (for read();) might (I'm not sure until the 
nightly builds are working again) prevent the bug from happening with 
var-blk records - but I think the 'bug' will still cause problems with 
fixed-block records and maybe other filetypes.  The issue I'm having is: 
raw_read() is setting devbufstart & devbufend, and raw_write() checks 
devbufend for buffering (which isn't required with var-block records or 
properly written fixed-block records in any case.)

My own feeling on this is, when reading tape-block data (fixed or variable 
blocks) and the blocks are not being buffered in calls (ie. my test-harness 
uses correctly sized buffers) then raw_read() shouldn't leave devbufstart or 
devbufend non-zero.

Hope this helps more,
Jason.

_________________________________________________________________
Personalise your phone with chart ringtones and polyphonics. Go to  
http://ringtones.com.au/ninemsn/control?page=/ninemsn/main.jsp


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