This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/2745] mutex with ERRORCHECK attribute fails to unlock on child after fork
- From: "jakub at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: 10 Jun 2006 08:58:03 -0000
- Subject: [Bug nptl/2745] mutex with ERRORCHECK attribute fails to unlock on child after fork
- References: <20060609191820.2745.rdabrowa@poczta.onet.pl>
- Reply-to: sourceware-bugzilla at sourceware dot org
------- Additional Comments From jakub at redhat dot com 2006-06-10 08:58 -------
What from "Consequently, to avoid errors, the child process may only execute
async-signal-safe operations until such time as one of the exec functions is
called." you don't understand?
In the child you of course are never supposed to unlock the lock, but instead
pthread_mutex_init it.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |INVALID
http://sourceware.org/bugzilla/show_bug.cgi?id=2745
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.