feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

analyzer: improve wording for "wrong mode" message

Browse Source 
Task-number: QTCREATORBUG-7747
Change-Id: I4a79e7d7047d6320f54824a019f98539d88a3c25
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@nokia.com>
This commit is contained in:
hjk
2012-08-22 14:39:48 +02:00
parent 25776a3a69
commit 3a8658496a
2 changed files with 21 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

19
doc/src/analyze/creator-valgrind.qdoc
View File

@@ -129,8 +129,8 @@
After you download and install Valgrind tools, you can use Callgrind from After you download and install Valgrind tools, you can use Callgrind from
\QC. \QC.
\note Callgrind is supported locally on Linux and Mac OS. You can run it on \note Callgrind is supported locally on Linux and Mac OS. You can run
a remote host from Windows. it on a remote Linux machine or device from any development machine.
To analyze applications: To analyze applications:
@@ -166,6 +166,21 @@
the \gui Callers view and about the called functions in the \gui Callees the \gui Callers view and about the called functions in the \gui Callees
view. view.
Since Debug and Release mode run-time characteristics differ
significantly, analytical findings for one mode may or not be
relevant for the other. Profiling a Debug mode build
often finds a major part of the time being spent in low-level
code like container implementations, while the same code
does not show up in the profile of a Release build of the
same application due to inlining and other optimizations
typically done there.
Many recent compilers allow you to build an optimized application
with debug information present at the same time. Typical
options for GCC are for instance \c{-g -O2}. It is
advisable to use such a setup for Callgrind profiling.
\image qtcreator-valgrind-callgrind.png "Profile view" \image qtcreator-valgrind-callgrind.png "Profile view"
\section1 Selecting Profiling Options \section1 Selecting Profiling Options

5
src/plugins/analyzerbase/analyzermanager.cpp
View File

@@ -515,7 +515,10 @@ void AnalyzerManagerPrivate::startLocalTool(IAnalyzerTool *tool)
const QString message = tr("<html><head/><body><p>You are trying " const QString message = tr("<html><head/><body><p>You are trying "
"to run the tool \"%1\" on an application in %2 mode. " "to run the tool \"%1\" on an application in %2 mode. "
"The tool is designed to be used in %3 mode.</p><p>" "The tool is designed to be used in %3 mode.</p><p>"
"Do you want to continue and run it in %2 mode?</p></body></html>") "Debug and Release mode run-time characteristics differ "
"significantly, analytical findings for one mode may or "
"may not be relevant for the other.</p><p>"
"Do you want to continue and run the tool in %2 mode?</p></body></html>")
.arg(toolName).arg(currentMode).arg(toolModeString); .arg(toolName).arg(currentMode).arg(toolModeString);
const QString checkBoxText = tr("&Do not ask again"); const QString checkBoxText = tr("&Do not ask again");
bool checkBoxSetting = false; bool checkBoxSetting = false;