This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/24443] Locking recursive mutex puts it into incorrect state with static linking
- From: "fweimer at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 11 Apr 2019 10:52:25 +0000
- Subject: [Bug nptl/24443] Locking recursive mutex puts it into incorrect state with static linking
- Auto-submitted: auto-generated
- References: <bug-24443-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=24443
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
--- Comment #3 from Florian Weimer <fweimer at redhat dot com> ---
It's a permanent solution. libpthread needs additional initialization, but the
functions called in your example to do not trigger linking with that (like
pthread_create does). In Fedora, we avoid this issue by always linking the
entirety of libpthread.a.
Maybe we should always perform the initialization steps required by libpthread,
avoid things issue.
--
You are receiving this mail because:
You are on the CC list for the bug.