This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH][BZ #12847] dprintf/vdprintf can cause fork to fail (child process crash)
- From: Roland McGrath <roland at hack dot frob dot com>
- To: Rich Felker <dalias at aerifal dot cx>
- Cc: OndÅej BÃlka <neleai at seznam dot cz>, libc-alpha at sourceware dot org
- Date: Wed, 25 Sep 2013 11:03:27 -0700 (PDT)
- Subject: Re: [PATCH][BZ #12847] dprintf/vdprintf can cause fork to fail (child process crash)
- Authentication-results: sourceware.org; auth=none
- References: <20130921191346 dot GA9202 at domone dot kolej dot mff dot cuni dot cz> <20130921194515 dot GF20515 at brightrain dot aerifal dot cx> <20130921202326 dot GA9893 at domone dot kolej dot mff dot cuni dot cz> <20130921214227 dot GG20515 at brightrain dot aerifal dot cx> <20130924210329 dot F00F22C097 at topped-with-meat dot com> <20130924213453 dot GO20515 at brightrain dot aerifal dot cx>
> No. Do you really want it as a separate bug rather than just a part of
> this existing one?
Yes. It's another change (and a user-visible one) that is not required to
fix the reported bug.
> If so, since dprintf is not required to be AS-safe,
> should it just be filed like a wishlist item?
Sure. Though, as the sole inventor of dprintf many years before it was
standardized, I can say authoritatively that it was always the intent that
it not have any more entanglements (i.e. potential failure modes) than
stack use and calling write. (That was never exactly true in the face of
user-defined printf extensions, but close enough.)
Thanks,
Roland