On 04/06/12 12:27, Christoph Bartoschek wrote: > how should one interpret the following report: > > Thread #11: Bug in libpthread: recursive write lock granted on > mutex/wrlock which does not support recursion > ==00:13:17:12.428 20623== at 0x4C2D18D: pthread_spin_lock (in > /usr/lib64/valgrind/vgpreload_helgrind-amd64-linux.so) > > > Is there a bug in libpthread that does something strange? Or is there a > bug in my program that tries to lock a lock twice?
It's saying that the program is trying to lock a mutex which is (a) already locked and (b) not marked as a recursive mutex. So yes, something is trying to lock the same mutex twice. Whether it is your program at fault is hard to say for sure without seeing the rest of the stack trace. Tom -- Tom Hughes ([email protected]) http://compton.nu/ ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
