This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug dynamic-link/14379] shared object constructors are called in the wrong order
- From: "luto at mit dot edu" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 02 Oct 2014 16:45:16 +0000
- Subject: [Bug dynamic-link/14379] shared object constructors are called in the wrong order
- Auto-submitted: auto-generated
- References: <bug-14379-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=14379
--- Comment #6 from Andy Lutomirski <luto at mit dot edu> ---
FWIW, in the comments to your patch, you mention that pthread_atfork is nearly
impossible to use cleanly without atomics. Unless I'm missing something, this
is true for the prepare handler, but not for the parent and child handlers --
there are no threads when the parent and child handlers are called.
--
You are receiving this mail because:
You are on the CC list for the bug.