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: Rich Felker <dalias at aerifal dot cx>
- To: Roland McGrath <roland at hack dot frob dot com>
- Cc: OndÅej BÃlka <neleai at seznam dot cz>, libc-alpha at sourceware dot org
- Date: Tue, 24 Sep 2013 17:34:53 -0400
- 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>
On Tue, Sep 24, 2013 at 02:03:29PM -0700, Roland McGrath wrote:
> > In principle, there's no good reason dprintf shouldn't be async-signal
> > safe, and it would be nice if it could eventually be so.
>
> Agreed. Have you filed a bug?
No. Do you really want it as a separate bug rather than just a part of
this existing one? If so, since dprintf is not required to be AS-safe,
should it just be filed like a wishlist item?
Rich