diff options
| author | Murray Read <ext-murray.2.read@nokia.com> | 2012-03-07 11:47:41 (GMT) |
|---|---|---|
| committer | Qt by Nokia <qt-info@nokia.com> | 2012-03-07 23:40:03 (GMT) |
| commit | 0ef9762bbb176c842a90bc5aaad49a7f2b054ad6 (patch) | |
| tree | 0ba00744201912aa509c2afa166a9efe916d40d9 /config.tests/qws/directfb | |
| parent | 3a57243fbffb771c0991c99d93ac9b9fcf4fc4ee (diff) | |
| download | Qt-0ef9762bbb176c842a90bc5aaad49a7f2b054ad6.zip Qt-0ef9762bbb176c842a90bc5aaad49a7f2b054ad6.tar.gz Qt-0ef9762bbb176c842a90bc5aaad49a7f2b054ad6.tar.bz2 | |
Don't allow app panic on QProcess destruction, kill or terminate
QProcess destruction will call kill() if the process is still running.
PRocess::Kill() and Terminate() both require the PowerMgmt capability
to operate on Symbian, otherwise a KERN-EXEC 46 panic happens.
An app should be able to use QProcess safely if it doesn't have
PowerMgmt capability, it should just be prevented from trying to kill
the created process. Now a debug message is issued on ~QProcess(),
kill() or terminate() if the capability is not present, rather than
actually trying to kill/terminate the process.
Task-number: ou1cimx1#985227
Change-Id: I3242ca2c39528c70c2c79e39f6a6384dd72f6ae6
Reviewed-by: Shane Kearns <shane.kearns@accenture.com>
Diffstat (limited to 'config.tests/qws/directfb')
0 files changed, 0 insertions, 0 deletions