Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Buffered stderr on Linux
- X-seq: zsh-workers 833
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Buffered stderr on Linux
- Date: Sat, 16 Mar 1996 10:46:33 -0800
- In-reply-to: Zoltan Hidvegi <hzoli@xxxxxxxxxx> "Re: Buffered stderr on Linux" (Mar 13, 12:17am)
- References: <199603122317.AAA10871@xxxxxxxxxxxxxxxxx>
- Reply-to: schaefer@xxxxxxx
On Mar 13, 12:17am, Zoltan Hidvegi wrote:
} Subject: Re: Buffered stderr on Linux
}
} Bart Schaefer wrote:
} > Stdio will call free() on the buffer at fclose().
}
} Well I've just checked it on Solaris and Linux and it seems that you are
} wrong.
Hm. I was sure that I remembered running into a multiple-free problem at
one point with this. However, the only notes I can find are about a case
where we avoided setbuf because we couldn't readily track the buffer pointer
all the way from setbuf to the fclose, and hence didn't know whether/when
to free it. So either I've got some cruft from a really obscure platform
floating around in my head, which is entirely possible, or I was confused.
Sorry about the false alarm.
--
Bart Schaefer
http://www.well.com/user/barts
Messages sorted by:
Reverse Date,
Date,
Thread,
Author