------- Comment #2 from Hans dot Boehm at hp dot com 2007-09-18 22:26 -------
I assume the LOCKED bit in *he is actually set when gdb looks at it? What does
the rest of the hash entry look like? That might give you a hint as to the
culprit.
Clearly someone sets the LOCKED bit on a hash entry and neglects to clear it.
If a compare_and_swap succeeded but returned failure anyway, that might explain
it. A misimplementation of release_set might also cause the problem. I don't
immediately see how this can be explained by a memory ordering issue.
--
Hans dot Boehm at hp dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |Hans dot Boehm at hp dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33479
