This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/14076] PTHREAD_MUTEX_LOCK() in multiple threads RETURNING EOWNERDEAD
- From: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Tue, 08 May 2012 13:49:58 +0000
- Subject: [Bug nptl/14076] PTHREAD_MUTEX_LOCK() in multiple threads RETURNING EOWNERDEAD
- Auto-submitted: auto-generated
- References: <bug-14076-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14076
Rich Felker <bugdal at aerifal dot cx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |bugdal at aerifal dot cx
--- Comment #1 from Rich Felker <bugdal at aerifal dot cx> 2012-05-08 13:49:58 UTC ---
Could you simplify the test case a bit and narrow down the cause of the bug? I
notice that you're using priority inheritance mutexes (which you didn't mention
in the report) which have some different code paths, so it would be helpful to
know if that's related to the problem.
Also, I'm not one of the glibc developers so you can take this or leave this,
but it would be nice if test cases could be C rather than C++, especially when
the C++ is gratuitous (in this case, just one use of a struct name as a type,
and a few references instead of pointers). Part of my reason for asking this is
that I like to test glibc testcases against my implementation of the C library
and on some of my test systems I don't have a C++ development environment.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.