On terça-feira, 10 de abril de 2012 21.44.49, Paul Floyd wrote: > > As for Qt 5, since locking and unlocking is inlined into the user code, > > valgrind might be completely unable to work. > > If the code is inline, then all I can think of would be to recognise the > opcode sequence and proceed from there.
It's very hard to distinguish a "lock cmpxchg" sequence doing locking from the
same code sequence doing something else, like allocating a timer ID in the
lock-free QFreeList.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Technology Center
Intel Sweden AB - Registration Number: 556189-6027
Knarrarnäsgatan 15, 164 40 Kista, Stockholm, Sweden
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
