[Development] No Finished signal from QProcess!

Thiago Macieira thiago.macieira at intel.com
Mon Feb 27 20:50:42 CET 2012

On terça-feira, 28 de fevereiro de 2012 01.02.25, lata agrawal wrote:
> Hi Thiago,


Please don't do top-posting to mailing lists.

> Thanks for replying. After reading on net, I found that "even if child
> process finishes and parent process is not waiting for the child process to
> finish, then parent process will not receive a finished signal. rather in
> this case, child process will become a zombie".

That "even" changes the meaning completely of the sentence. If you leave it 
out, the sentence makes sense for the generic case.

It does not apply to QProcess though: QProcess is always waiting for the child 
process to finish.

> I checked that after using waitforfinished(), I was getting finished
> signal. I will send you minimal compilable code.
> Is there any solution where I can get finished signal from child process
> without waiting for it.

That question does not make sense. QProcess is always waiting for the signal, 
which is delivered asynchronously.

Note: you're posting to the mailing list discussion development _of_ Qt. I am 
assuming that you have run into a situation that you believe to be due to a Qt 
bug. When you send the testcase, I will not be trying to fix it for you -- that 
is not the intention of this mailing list. 

If you are uncertain whether your code is correct, then we're talking about 
development *with* Qt. That's the interest at qt-project.org mailing list. Please 
post there if that's the case.

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.qt-project.org/pipermail/development/attachments/20120227/22e3daf8/attachment.sig>

More information about the Development mailing list