From:	Carsten DOT Roedel AT rt DOT bosch DOT de (Carsten Roedel K8/DIC2 Tel. 4276)
Subject:	B19.1 ftell(), fseek() bug
14 May 1998 11:24:04 -0700 :
Message-ID:	<199805140759.JAA11137.cygnus.gnu-win32@dione>
To:	gnu-win32 AT cygnus DOT com

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 AT cygnus DOT com" with one line of text: "help".

- Raw text -