[Interest] llvm thread sanitizer and qmutex

[Firl, Benjamin]

Thanks for your responses. So it seems our only option is to (automatically) replace every mutex with boost::mutex for debugging. 
I will also post the bug regarding global objects to LLVM.


-----Original Message-----
From: interest-bounces+benjamin.firl=wincor-nixdorf.com at qt-project.org [mailto:interest-bounces+benjamin.firl=wincor-nixdorf.com at qt-project.org] On Behalf Of Thiago Macieira
Sent: Wednesday, March 05, 2014 5:04 PM
To: interest at qt-project.org
Subject: Re: [Interest] llvm thread sanitizer and qmutex

Em qua 05 mar 2014, às 16:01:13, Konrad Rosenbaum escreveu:
> Valgrind is confused by this as well...

Valgrind usually comes with intercepts for QMutex. It did for Qt 4, at least. 
I don't know whether it's been updated for Qt 5 yet.

Just be glad we didn't leave the locking function inline. Then it would be 
impossible to intercept...

-- 
Thiago Macieira - thiago.macieira (AT) intel.com
  Software Architect - Intel Open Source Technology Center

_______________________________________________
Interest mailing list
Interest at qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest