This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug dynamic-link/21777] use of pthread_getspecific, pthread_setspecific in a statically linked program leads to a crash before main
- From: "ppluzhnikov at google dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Sun, 02 Sep 2018 17:58:24 +0000
- Subject: [Bug dynamic-link/21777] use of pthread_getspecific, pthread_setspecific in a statically linked program leads to a crash before main
- Auto-submitted: auto-generated
- References: <bug-21777-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=21777
Paul Pluzhnikov <ppluzhnikov at google dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |MOVED
--- Comment #5 from Paul Pluzhnikov <ppluzhnikov at google dot com> ---
(In reply to Bruno Haible from comment #4)
> So, pthread_setspecific and pthread_mutex* are different techniques for
> making a program multithread-safe.
That's fair.
The problem is in libgcc.
I filed https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87189.
--
You are receiving this mail because:
You are on the CC list for the bug.