Utils: Drop QProcess specific parameters from QtcProcess::finished()

Mid-term plan is to concentrate on use of QtcProcess::result()
instead which is a bit more system-agnostic.

There's quite a bit of potential for downstream cleanup by
re-using QtcProcess::exitMessage() now.

Change-Id: I3806b3f5933d96e64b7cfb18cc6c52823fddcbcd
Reviewed-by: Christian Stenger <[email protected]>

1 files changed, 4 insertions, 3 deletions

diff --git a/src/plugins/languageclient/languageclientinterface.cpp b/src/plugins/languageclient/languageclientinterface.cpp
index a12472526ef..99a9c0d41bd 100644
--- a/src/plugins/languageclient/languageclientinterface.cpp
+++ b/src/plugins/languageclient/languageclientinterface.cpp
@@ -134,10 +134,11 @@ void StdIOClientInterface::sendData(const QByteArray &data)
     m_process.write(data);
 }
 
-void StdIOClientInterface::onProcessFinished(int exitCode, QProcess::ExitStatus exitStatus)
+void StdIOClientInterface::onProcessFinished()
 {
-    if (exitStatus == QProcess::CrashExit)
-        emit error(tr("Crashed with exit code %1: %2").arg(exitCode).arg(m_process.errorString()));
+    if (m_process.exitStatus() == QProcess::CrashExit)
+        emit error(tr("Crashed with exit code %1: %2")
+                       .arg(m_process.exitCode()).arg(m_process.errorString()));
     emit finished();
 }