X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10112131508.AA15003@clio.rice.edu>
Subject: Re: A buffering problem?
To: eliz AT is DOT elta DOT co DOT il
Date: Thu, 13 Dec 2001 09:08:33 -0600 (CST)
Cc: djgpp-workers AT delorie DOT com, tim DOT van DOT holder AT pandora DOT be,
   laszlo DOT molnar AT eth DOT ericsson DOT se
In-Reply-To: <3995-Thu13Dec2001095453+0200-eliz@is.elta.co.il> from "Eli Zaretskii" at Dec 13, 2001 09:54:53 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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
Precedence: bulk

> > This is a shot in the dark - but what if in frlist.c (intial file structure
> > setup) we tested each file handle (with _get_dev_info?) before putting that 
> > file structure in the initial list?
> 
> Will that work on W2K, given the problems with _get_dev_info there?

get_dev_info returns -1 on invalid handles, which is all we need to
know for sure.  

> In any case, this will solve the case where a parent program closes
> one of the standard streams, but not a more general problem with
> closing a file handle that belongs to a FILE object.

Agreed.  And I'm not sure the above fixes anything, yet.

> But if it's safe for W2K, then it might be worthwhile to put this into
> the 2.03 refresh.

Unless we have proof it fixes something, I'd rather not do anything at all
to the refresh right now.