From 966498f9a43f116a329f74674e4dc50e35969c2f Mon Sep 17 00:00:00 2001 From: Christian Stenger Date: Fri, 18 Nov 2022 12:42:39 +0100 Subject: [PATCH] PerfProfiler: Be more verbose when running perf If perf cannot be started for whatever reasons it is quite hard to figure out its reason. Add a note how perf is started and give some hint on the application output pane as the message box points the user to it. Task-number: QTCREATORBUG-28462 Change-Id: I4d386078f6e3719fefc9b3dc7d77fffbdb294030 Reviewed-by: hjk --- src/plugins/perfprofiler/perfprofilerruncontrol.cpp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/plugins/perfprofiler/perfprofilerruncontrol.cpp b/src/plugins/perfprofiler/perfprofilerruncontrol.cpp index 54b1b80fb4e..a5873dcfc50 100644 --- a/src/plugins/perfprofiler/perfprofilerruncontrol.cpp +++ b/src/plugins/perfprofiler/perfprofilerruncontrol.cpp @@ -115,6 +115,8 @@ public: reportFailure(msg); return; } + if (!m_process->cleanedStdErr().isEmpty()) + appendMessage(m_process->cleanedStdErr(), Utils::StdErrFormat); reportStopped(); }); @@ -125,6 +127,7 @@ public: m_process->setCommand(cmd); m_process->setWorkingDirectory(runControl()->workingDirectory()); + appendMessage("Starting Perf: " + cmd.toUserOutput(), Utils::NormalMessageFormat); m_process->start(); }