[mailto:interest-bounces+benjamin.firl=wincor-nixdorf@qt-project.org] On
Behalf Of Thiago Macieira
Sent: Wednesday, March 05, 2014 5:04 PM
To: interest@qt-project.org
Subject: Re: [Interest] llvm thread sanitizer and qmutex
Em qua 05 mar 2014, às 16:01:13, Konrad Rosenbaum escreveu:
> Valgrind
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
Hi,
On Wednesday, Wednesday 05 March 2014 at 14:50, Firl, Benjamin wrote:
> we make heavy use of Qt in our software and are now trying to use llvm
> thread sanitizer for debugging. Unfortunately the sanitizer doesn't seem
> to recognize QMutex as a locking mechanism.
That's because on Linux it do
Hallo,
we make heavy use of Qt in our software and are now trying to use llvm thread
sanitizer for debugging. Unfortunately the sanitizer doesn't seem to recognize
QMutex as a locking mechanism.
The example below warns about a race condition because the member "data" is
accessed in two threads.
