X-Authentication-Warning:	delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Date:	Fri, 11 Jan 2002 19:26:35 +0200
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
Message-Id:	<3099-Fri11Jan2002192635+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.1.50 (via feedmail 8 I) and Blat ver 1.8.9
CC:	djgpp-workers AT delorie DOT com
In-reply-to:	<10201111628.AA15029@clio.rice.edu> (sandmann@clio.rice.edu)
Subject:	Re: frlist.c proposed patch
References:	<10201111628 DOT AA15029 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: Fri, 11 Jan 2002 10:28:00 -0600 (CST)
> 
> Let's take a pathological case:
>  1) parent closes handles 1..4 (including stdout)
>  2) child opens a file, writes to it (it is assigned handle 1)
>  3) child prints to stdout() - it also goes to his file (uggh) and the
>     buffers are all messed up

That's _real_ pathological: no parent program in their right mind
should close stdout .

> So, when I do the stdout setup and notice that fileno(stdout) is not
> open - I'm saying I should change the file structure to cause failures
> instead of stomping on another file.

Maybe just put some impossible number, like -1 or something, instead
of the handles in those FILE objects which are supposed to be
preconnected.

- Raw text -