On Tue, 2012-06-05 at 18:03 +0200, Christoph Bartoschek wrote:
> I am sure that the spin lock is not used recursively because the code
> basically looks like this:
>
> mutex m;
> int data = 0;
>
> int func()
> {
> m.lock();
> int ret = ++data;
> m.unlock();
> return ret;
> }
>
> This is the only occurence of the lock.
Well, then that looks like a real bug in the pthread lib
(or a bug in the Valgrind simulation e.g. of atomic instructions use
by the pthread lib ?).
If you have a small reproducer, that will help to dig into the problem.
Otherwise, gdb on Valgrind and/or Valgrind gdbserver might help
you to see what is going (wrong).
Philippe
------------------------------------------------------------------------------
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
