X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
Subject: Re: A buffering problem?
From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Cc: sandmann AT clio DOT rice DOT edu, djgpp-workers AT delorie DOT com,
   laszlo DOT molnar AT eth DOT ericsson DOT se
In-Reply-To: <8582-Thu13Dec2001101431+0200-eliz@is.elta.co.il>
References:  <10112121907 DOT AA18276 AT clio DOT rice DOT edu> 
	<8582-Thu13Dec2001101431+0200-eliz AT is DOT elta DOT co DOT il>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
X-Mailer: Evolution/1.0 (Preview Release)
Date: 13 Dec 2001 09:40:49 +0100
Message-Id: <1008232851.29299.0.camel@bender.falconsoft.be>
Mime-Version: 1.0
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

On Thu, 2001-12-13 at 09:14, Eli Zaretskii wrote:
> This cannot be the whole story, or maybe I'm missing some detail.
> 
> If stdaux is closed with fclose, that sets the _flag member of its
> FILE object to zero.  _fwalk (invoked by stdout hook at exit time)
> ignores any FILE objects whose _flag is zero.  So it won't do
> anything with the stale stdaux.
> 
> Unfortunately, even after reading the archives on DJ's server, I
> cannot figure out what else was involved.  Unless this happens in a
> child program whose parent closed stdaux, that is; is that the case in
> point?

That was the case with autoconf, yes - autoconf caused perl to run,
which closed stdaux & stdprn.  Then when autoconf ran m4, its output was
screwed up (because it wrote to fd 3, which didn't get flushed).