This is the mail archive of the glibc-bugs@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug stdio/20200] dprintf unconditionally calls malloc


https://sourceware.org/bugzilla/show_bug.cgi?id=20200

--- Comment #5 from Carlos O'Donell <carlos at redhat dot com> ---
(In reply to Florian Weimer from comment #4)
> > > It's a regression in 2.23.  It's fix probably will not address the other
> > > issues in bug 16060.
> > 
> > What's the regression?
> 
> Before, you could call dprintf from a signal handler, interrupting malloc,
> and it would work if the format string was reasonable (no self-deadlock). 
> After the change to use malloc for the temporary buffer instead of mmap, you
> end up with a self-deadlock.

We might document asprintf as being conditionally AS-safe, but what might the
conditions of safety be?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]