On terça-feira, 10 de abril de 2012 22.46.38, Paul Floyd wrote:
> On 10 Apr 2012, at 22:28, Thiago Macieira wrote:
> > 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 una
On 10 Apr 2012, at 22:28, Thiago Macieira wrote:
> 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 wo
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 fro
On 10 Apr 2012, at 14:56, Thiago Macieira wrote:
>
> That's not correct. Valgrind's helgrind had support for QMutex specifically.
> Helgrind needed to know when a mutex was locked or unlocked, in order to
> present its warnings. To do that, it specifically overrides the QMutex::lock
> and unl
On terça-feira, 10 de abril de 2012 13.35.24, pa...@free.fr wrote:
> - Original Message -
>
> > Hi all...what's the best tool to detect threading errors in qt5 based
> > code?
> > Are valgrind's drd and helgrind tools reliable for qt5 code?
> > AFAIK they include some support for qt4 based
- Original Message -
> Hi all...what's the best tool to detect threading errors in qt5 based
> code?
> Are valgrind's drd and helgrind tools reliable for qt5 code?
> AFAIK they include some support for qt4 based clients, but I also
> know Qmutex has changed quite a lot in qt5, so I wonder i
