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

Debugger: Use Utils::QtcProcess instead of GdbProcess

Browse Source 
The original use case of running GDB itself remotely
is not present anymore.

Change-Id: I283a27216d6a8849fea7d9ca8df6b94571fb99fd
Reviewed-by: Christian Stenger <christian.stenger@theqtcompany.com>
This commit is contained in:
hjk
2015-06-08 12:10:11 +02:00
parent ad51a43c73
commit 03212d6e49
11 changed files with 43 additions and 252 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/plugins/debugger/gdb/gdbplainengine.cpp
View File

@@ -29,7 +29,6 @@
****************************************************************************/
#include "gdbplainengine.h"
#include "gdbprocess.h"
#include <debugger/debuggeractions.h>
#include <debugger/debuggercore.h>
@@ -127,9 +126,10 @@ void GdbPlainEngine::setupEngine()
gdbArgs.append(_("--tty=") + m_outputCollector.serverName());
if (!runParameters().workingDirectory.isEmpty())
m_gdbProc->setWorkingDirectory(runParameters().workingDirectory);
if (runParameters().environment.size())
m_gdbProc->setEnvironment(runParameters().environment.toStringList());
m_gdbProc.setWorkingDirectory(runParameters().workingDirectory);
Utils::Environment env = runParameters().environment;
if (env.size())
m_gdbProc.setEnvironment(env);
startGdb(gdbArgs);
}