Am 04.06.2012 14:00, schrieb Tom Hughes:
> 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.
Thanks,
however I wonder that the message does not mention where the lock was
aquired for the first time.
This is how the complete message looks like:
Thread #14: Bug in libpthread: recursive write lock granted on
mutex/wrlock which does not support recursion
at 0x4C2D18D: pthread_spin_lock (in
/usr/lib64/valgrind/vgpreload_helgrind-amd64-linux.so)
by 0x67B8E9: legos::spin_np_t::lock__default(legos::spin_np_t*) (in
nutsh-O)
by 0xE1E7F30: IJMQueue::remove(IJMPropertyOwner*, int) (in src-O.dll)
by 0xE1E4CD5: IJMTimingPoint::removeATQ() (in src-O.dll)
by 0x105D3577: IJMHierBox::theATQueueThreadFunc(void*) (in engine-O.dll)
by 0x4C2C03D: ??? (in
/usr/lib64/valgrind/vgpreload_helgrind-amd64-linux.so)
by 0x503DF04: start_thread (in /lib64/libpthread-2.14.1.so)
by 0x5CAD10C: clone (in /lib64/libc-2.14.1.so)
Christoph
------------------------------------------------------------------------------
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
