Application leads to hang on continuously reading from QProcess stdout

[ChrisW67]

Are you really polling the standard output of the sub-process 100,000 times per second on the chance that there is some output? Seems you should just be waiting for readyReadStdout() to be emitted and then read (a separate thread may not be needed).

This could be a deadlock caused by unsynchronised access from multiple threads. It could be a memory leak finally crippling the program after 30 minutes.

[venk2ksubbu]

Thank you for the quick reply Chris.

Yes, there is chance of having data to read after every 10 micro seconds.
I could use the readyReadStdout() signal, but that may not give performance like
the thread.

I will give a try.

Regards,
Subbarao

[venk2ksubbu]

Use of readyReadStdout did not help as the thread waiting for output was timing out.
There seems to be a deadlock because of two Mutexes in the present implementation.

Can you please suggest a tool which I can use to detect deadlock ?

I tried with Helgrind (part of valgrind 2.2.0). But the valgrind itself crashed due to bug in it.
Also I cannot use latest valgrind as this does not support Helgrind.

Thanks in advance,
Subbarao