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

Valgrind: Shorten and correct start action name

Browse Source 
The applications to attach to do not have to be remote at all.
Also, the name should be as short as possible as space in the
status bar is not unlimited.

Change-Id: I1df8e025114cd8ad94daa5219c26e61ce70e5e5d
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
This commit is contained in:
hjk
2016-03-02 18:07:58 +01:00
parent bd29c4ba09
commit c326011feb
3 changed files with 3 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -277,8 +277,7 @@
\list 1
\li Select \uicontrol Analyze > \uicontrol {Valgrind Memory Analyzer (External
Remote Application)} or
\uicontrol {Valgrind Function Profiler (External Remote Application)}.
Application)} or \uicontrol {Valgrind Function Profiler (External Application)}.
\image qtcreator-valgrind-remote-settings.png "Start Analyzer dialog"

2
src/plugins/valgrind/callgrindtool.cpp
View File

@@ -247,7 +247,7 @@ CallgrindTool::CallgrindTool(QObject *parent)
AnalyzerManager::registerAction(CallgrindLocalActionId, desc);
}
desc.setText(tr("Valgrind Function Profiler (External Remote Application)"));
desc.setText(tr("Valgrind Function Profiler (External Application)"));
desc.setPerspectiveId(CallgrindPerspectiveId);
desc.setCustomToolStarter([this](ProjectExplorer::RunConfiguration *runConfig) {
StartRemoteDialog dlg;

2
src/plugins/valgrind/memchecktool.cpp
View File

@@ -315,7 +315,7 @@ MemcheckTool::MemcheckTool(QObject *parent)
AnalyzerManager::registerAction("MemcheckWithGdb.Local", desc);
}
desc.setText(tr("Valgrind Memory Analyzer (External Remote Application)"));
desc.setText(tr("Valgrind Memory Analyzer (External Application)"));
desc.setPerspectiveId(MemcheckPerspectiveId);
desc.setCustomToolStarter([this](ProjectExplorer::RunConfiguration *runConfig) {
StartRemoteDialog dlg;