From c4f9c6f265c28ed5602646c0fd147f4066d83205 Mon Sep 17 00:00:00 2001 From: Volker Vogelhuber Date: Tue, 26 Apr 2016 09:52:42 +0200 Subject: [PATCH] fix environment variables on remote valgrind Change-Id: I01836cf90d4d905d5edc859e110372a6e634a683 Reviewed-by: hjk Reviewed-by: Christian Kandeler --- src/plugins/valgrind/valgrindprocess.cpp | 3 +++ 1 file changed, 3 insertions(+) diff --git a/src/plugins/valgrind/valgrindprocess.cpp b/src/plugins/valgrind/valgrindprocess.cpp index b4894f5066f..c9e27dfcca7 100644 --- a/src/plugins/valgrind/valgrindprocess.cpp +++ b/src/plugins/valgrind/valgrindprocess.cpp @@ -216,6 +216,9 @@ void ValgrindProcess::connected() cmd += m_valgrindExecutable + QLatin1Char(' ') + argumentString(Utils::OsTypeLinux); m_remote.m_process = m_remote.m_connection->createRemoteProcess(cmd.toUtf8()); + for (auto it = m_debuggee.environment.constBegin(); it != m_debuggee.environment.constEnd(); ++it) + m_remote.m_process->addToEnvironment(it.key().toUtf8(), it.value().toUtf8()); + connect(m_remote.m_process.data(), &QSsh::SshRemoteProcess::readyReadStandardError, this, &ValgrindProcess::handleRemoteStderr); connect(m_remote.m_process.data(), &QSsh::SshRemoteProcess::readyReadStandardOutput,