forked from qt-creator/qt-creator
Valgrind: Make callgrind work on docker
Callgrind on Remote Linux did not work for years, so its safe to ignore the remains from the previous remote support and start over. This here now handles the local case and the case where callgrind runs together with the debuggee in the same docker container. Guessing at the output file name is replaced by specifiying it in advance. Cross-setups are not yet supported. Change-Id: I97edeb4eab7475727eddb26d25f8bec650a7eeb9 Reviewed-by: Christian Stenger <christian.stenger@qt.io>
This commit is contained in:
@@ -70,10 +70,11 @@ private:
|
||||
void showStatusMessage(const QString &message);
|
||||
|
||||
void triggerParse();
|
||||
void localParseDataAvailable(const QString &file);
|
||||
void handleLocalParseData(const Utils::FilePath &filePath);
|
||||
void controllerFinished(Callgrind::CallgrindController::Option option);
|
||||
|
||||
bool m_markAsPaused = false;
|
||||
Utils::FilePath m_valgrindOutputFile;
|
||||
Callgrind::CallgrindController m_controller;
|
||||
Callgrind::Parser m_parser;
|
||||
bool m_paused = false;
|
||||
|
||||
Reference in New Issue
Block a user