Re: B19.1 ftell(), fseek() bug

["Steve Biskis" <mlx at san dot rr dot com>]

Simplest solution:

NEVER use fopen in text mode.
ONLY use fopen in binary mode.

da bisk

----------
> From: Carsten Roedel K8/DIC2 Tel. 4276 <Carsten.Roedel@rt.bosch.de>
> To: gnu-win32@cygnus.com
> Subject: B19.1 ftell(), fseek() bug
> Date: Thursday, May 14, 1998 12:59 AM
> 
> I discovered a problem with ftell() and fseek() in cygwin32-B19.1 under
Win95.
> The problem is, when passing the position got from ftell() to fseek(),
> it does not end up at the same location!? Apparantly ftell does account
> the <cr>/<lf> in the byte stream, where fseek does NOT! It seems that
> fseek skips the <cr> bytes. I think that the ftell behaviour is correct,
> it should always tell the correct position in any byte stream, as it
does.
> But, however, it is obvious that ftell and fseek must match together to
> be compatible. 
> 
> As I must get cvs/rcs run on my machine (that's where I discovered the
wrong 
> behavior) I can't wait for a patch. Could someone give me a hint how to
continue?
> Is it worth to load the source code and try to compile gnu-win32 by
myself?
> 
> Any help would be appreciated
> 
> Carsten
> :-) Always remember to keep smiling
> -
> For help on using this list (especially unsubscribing), send a message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".