Am 29.06.2012 15:46, schrieb Alexander Potapenko: > This may be not that easy to guess which locks are taken when the > deadlock has already occurred. > However a Valgrind-like tool is really an overkill for deadlock > detection: a small library that interposes pthread_mutex_* (or other > locking primitives) and keeps track of the locking order is fairly > enough.
In a deadlock all threads wait on the same lock. It should be easy to find it. 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 Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
