[Bug malloc/16159] malloc_printerr() deadlock, when calling malloc_printerr() again
joseph at codesourcery dot com
sourceware-bugzilla@sourceware.org
Wed Nov 13 16:47:00 GMT 2013
http://sourceware.org/bugzilla/show_bug.cgi?id=16159
--- Comment #15 from joseph at codesourcery dot com <joseph at codesourcery dot com> ---
On Wed, 13 Nov 2013, neleai at seznam dot cz wrote:
> Why did you jump from dlopening to static linking? Dynamic linking would
> work and if there is concern that user does not have one we could
> provide a stub implementation and function to test if we deal with stub
> or real one.
I don't think default dlopening libgcc_s from libc at startup is desirable
on performance grounds (most programs will never need it), whereas from
libpthread it's likely to be less significant.
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Glibc-bugs
mailing list