Valgrind: Start custom actions more directly

This does not need to go through the PE machinery.

Change-Id: If0b2fde5309d7e119e8ac27245a22939b68d847d
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
This commit is contained in:
hjk
2015-06-19 08:34:46 +02:00
parent 8a1c603c0d
commit 92ec05c9bd
7 changed files with 42 additions and 28 deletions

View File

@@ -120,7 +120,7 @@ public:
void doClear(bool clearParseData);
void updateEventCombo();
AnalyzerRunControl *createRunControl(const AnalyzerStartParameters &sp,
ValgrindRunControl *createRunControl(const AnalyzerStartParameters &sp,
RunConfiguration *runConfiguration = 0);
signals:
@@ -514,13 +514,13 @@ CallgrindTool::~CallgrindTool()
delete d;
}
AnalyzerRunControl *CallgrindTool::createRunControl(const AnalyzerStartParameters &sp,
ValgrindRunControl *CallgrindTool::createRunControl(const AnalyzerStartParameters &sp,
RunConfiguration *runConfiguration)
{
return d->createRunControl(sp, runConfiguration);
}
AnalyzerRunControl *CallgrindToolPrivate::createRunControl(const AnalyzerStartParameters &sp,
ValgrindRunControl *CallgrindToolPrivate::createRunControl(const AnalyzerStartParameters &sp,
RunConfiguration *runConfiguration)
{
CallgrindRunControl *rc = new CallgrindRunControl(sp, runConfiguration);