From: Oliver Neukum <[EMAIL PROTECTED]>
if a driver returns an error in fill_read_buffer(), the buffer will be
marked as filled. Subsequent reads will return eof. But there is
no data because of an error, not because it has been read.
Not marking the buffer filled is the obvious fix.
From: Oliver Neukum [EMAIL PROTECTED]
if a driver returns an error in fill_read_buffer(), the buffer will be
marked as filled. Subsequent reads will return eof. But there is
no data because of an error, not because it has been read.
Not marking the buffer filled is the obvious fix.
Am Dienstag, 2. Januar 2007 16:47 schrieb Alan Stern:
> On Tue, 2 Jan 2007, Oliver Neukum wrote:
>
> > Am Dienstag, 2. Januar 2007 16:26 schrieb Alan Stern:
> > > On Tue, 2 Jan 2007, Oliver Neukum wrote:
> > >
> > > > Hi,
> > > >
> > > > if a driver returns an error in fill_read_buffer(), the
On Tue, 2 Jan 2007, Oliver Neukum wrote:
> Am Dienstag, 2. Januar 2007 16:26 schrieb Alan Stern:
> > On Tue, 2 Jan 2007, Oliver Neukum wrote:
> >
> > > Hi,
> > >
> > > if a driver returns an error in fill_read_buffer(), the buffer will be
> > > marked as filled. Subsequent reads will return
Am Dienstag, 2. Januar 2007 16:26 schrieb Alan Stern:
> On Tue, 2 Jan 2007, Oliver Neukum wrote:
>
> > Hi,
> >
> > if a driver returns an error in fill_read_buffer(), the buffer will be
> > marked as filled. Subsequent reads will return eof. But there is
> > no data because of an error, not
On Tue, 2 Jan 2007, Oliver Neukum wrote:
> Hi,
>
> if a driver returns an error in fill_read_buffer(), the buffer will be
> marked as filled. Subsequent reads will return eof. But there is
> no data because of an error, not because it has been read.
> Not marking the buffer filled is the obvious
On Tue, 2 Jan 2007, Oliver Neukum wrote:
Hi,
if a driver returns an error in fill_read_buffer(), the buffer will be
marked as filled. Subsequent reads will return eof. But there is
no data because of an error, not because it has been read.
Not marking the buffer filled is the obvious fix.
Am Dienstag, 2. Januar 2007 16:26 schrieb Alan Stern:
On Tue, 2 Jan 2007, Oliver Neukum wrote:
Hi,
if a driver returns an error in fill_read_buffer(), the buffer will be
marked as filled. Subsequent reads will return eof. But there is
no data because of an error, not because it has
On Tue, 2 Jan 2007, Oliver Neukum wrote:
Am Dienstag, 2. Januar 2007 16:26 schrieb Alan Stern:
On Tue, 2 Jan 2007, Oliver Neukum wrote:
Hi,
if a driver returns an error in fill_read_buffer(), the buffer will be
marked as filled. Subsequent reads will return eof. But there is
Am Dienstag, 2. Januar 2007 16:47 schrieb Alan Stern:
On Tue, 2 Jan 2007, Oliver Neukum wrote:
Am Dienstag, 2. Januar 2007 16:26 schrieb Alan Stern:
On Tue, 2 Jan 2007, Oliver Neukum wrote:
Hi,
if a driver returns an error in fill_read_buffer(), the buffer will be
Hi,
if a driver returns an error in fill_read_buffer(), the buffer will be
marked as filled. Subsequent reads will return eof. But there is
no data because of an error, not because it has been read.
Not marking the buffer filled is the obvious fix.
Regards
Oliver
Hi,
if a driver returns an error in fill_read_buffer(), the buffer will be
marked as filled. Subsequent reads will return eof. But there is
no data because of an error, not because it has been read.
Not marking the buffer filled is the obvious fix.
Regards
Oliver
12 matches
Mail list logo