Re: Fwd: Bug#43023: libc 2.1.1-10 makes it impossible to use stdout reliably

[Brendan Cully <brendan@kublai.com>]

On Sunday, 15 August 1999 at 21:46, Alex Buell wrote:
> On Sun, 15 Aug 1999, Joel Klecker wrote:
> 
> > However, stdio buffers things.  In many cases, the data doesn't get
> > written until the program returns from main or calls exit(3).
> > Furthermore there exist a number of network filesystems and similar
> > systems where write errors are not reported until close(2).  So a
> > straightforward `hello world' program, for example, might well lose
> > data, even if it checked the return from printf(3).
> 
> BOLLOCKS, COMPLETE BOLLOCKS.  Three choices: 1) Don't use stdio 2) turn
> buffering off 3) use fflush(). Read the info files for further
> information.
> 
> *plonk*
> 
> I don't like trolls.
> 
> Cheers, 
> Alex 

What?! Read further down. He's complaining that libc segfaults on
fclose(STDOUT).

-- 
Brendan Cully <brendan@kublai.com> | OLD SKOOL ROOLZ
"I hope I don't win                |          .-_|\ 
 The rules say to bring a friend   |         /     \
 I don't have any"                 | Perth ->*.--._/