Valgrind: Fix display name for analyzing remote external application.

The current one just adds the string "(Remote)", which is pretty much
guaranteed to trick users into thinking it's the one they must choose
when running remote valgrind. Instead, we must make it clear that it's
for analyzing something other than the current project. Unfortunately,
the string still contains the word "remote" because for some reason,
we don't offer valgrind for local external applications.

Change-Id: I27296851b747437e96dc22dbaf54eaf10dcf4be5
Reviewed-by: hjk <hjk121@nokiamail.com>
This commit is contained in:
Christian Kandeler
2014-04-25 15:09:22 +02:00
committed by hjk
parent 1edc65cc1b
commit f0594a0d61

View File

@@ -150,7 +150,7 @@ bool ValgrindPlugin::initialize(const QStringList &, QString *)
action = new ValgrindAction(this);
action->setId("Memcheck.Remote");
action->setTool(m_memcheckTool);
action->setText(tr("Valgrind Memory Analyzer (Remote)"));
action->setText(tr("Valgrind Memory Analyzer (External Remote Application)"));
action->setToolTip(memcheckToolTip);
action->setMenuGroup(Constants::G_ANALYZER_REMOTE_TOOLS);
action->setStartMode(StartRemote);
@@ -159,7 +159,7 @@ bool ValgrindPlugin::initialize(const QStringList &, QString *)
action = new ValgrindAction(this);
action->setId("Callgrind.Remote");
action->setTool(m_callgrindTool);
action->setText(tr("Valgrind Function Profiler (Remote)"));
action->setText(tr("Valgrind Function Profiler (External Remote Application)"));
action->setToolTip(callgrindToolTip);
action->setMenuGroup(Constants::G_ANALYZER_REMOTE_TOOLS);
action->setStartMode(StartRemote);