This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/16657] Lock elision breaks pthread_mutex_destroy
- From: "jmbnyc at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Wed, 02 Jul 2014 18:18:26 +0000
- Subject: [Bug nptl/16657] Lock elision breaks pthread_mutex_destroy
- Auto-submitted: auto-generated
- References: <bug-16657-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16657
--- Comment #22 from Jeffrey M. Birnbaum <jmbnyc at gmail dot com> ---
Well, I find that comment somewhat offensive, i.e. a bug in my code. I only
showed an outline so that you could comment on whether or not the trylock
elision issue was related to what I am observing.
I can certainly understand why you would say that given that a reproducible
test is the best proof of an issue. However, in your response you said "if you
have more information, please share" so that is what I did. I'm not sure I
deserved the "well, most likely a bug in your code where you don't sync
read/write properly".
Regardless, I will try to create a simple test case the repro's the issue. I
can assure you that there are no other variables involved in what I described
that come into play. In fact, the description is almost verbatim the code. The
only shared object is the pthread mutex and I think that was fairly clear from
the code snippet.
--
You are receiving this mail because:
You are on the CC list for the bug.