Date:	Mon, 20 Aug 2001 08:22:59 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id:	<9003-Mon20Aug2001082258+0300-eliz@is.elta.co.il>
X-Mailer:	Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.9
CC:	acottrel AT ihug DOT com DOT au, djgpp-workers AT delorie DOT com
In-reply-to:	<10108200407.AA18104@clio.rice.edu> (sandmann@clio.rice.edu)
Subject:	Re: Fseek on STDIN problem on Win 2K
References:	<10108200407 DOT AA18104 AT clio DOT rice DOT edu>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
> Date: Sun, 19 Aug 2001 23:07:28 -0500 (CDT)
> 
> 1) I build this, and I see the same problem on W2K and XP
> 2) Same binary, if I set lfn=n then it works fine.
> 3) Same source, but built with V2.03 library works.
> 
> So, it appears related to LFN stuff, and it appears it was broken after V2.03.
> 
> If I remove the fseek(pfp, 0, Seek_set) there is no change in the strange
> behavior.

Which change in the behavior is that?  Do you mean that after removing
fseek, both LFN=y and LFN=n behave the same way?  Or do you mean that
binaries built with v2.03 and with CVS work the same?

> If I remove the fstat at the beginning of this code (and hardwire pfp) the
> problem goes away.  I'm guessing we are reading the magic number in fstat
> and the pointer isn't getting set correctly?

Yes, probably.  But is_exec.c returns the position to where it found
it, so...

- Raw text -