QNX: Fixed starting executable when debugging on QNX Neutrino device

An updated version of gdb for QNX does not support "-exec-run" with path parameter,
while "run" still works.

Change-Id: I86bbe3ef2247809e56416ed641df5bc8e165fddd
Reviewed-by: hjk <qthjk@ovi.com>
This commit is contained in:
Tobias Nätterlund
2012-08-24 07:58:28 +02:00
committed by hjk
parent 61e95e9a99
commit 526c2bfe7e

View File

@@ -347,7 +347,9 @@ void GdbRemoteServerEngine::runEngine()
const QString remoteExecutable = startParameters().remoteExecutable; const QString remoteExecutable = startParameters().remoteExecutable;
if (!remoteExecutable.isEmpty()) { if (!remoteExecutable.isEmpty()) {
postCommand("-exec-run " + remoteExecutable.toLocal8Bit(), GdbEngine::RunRequest, CB(handleExecRun)); // Cannot use -exec-run for QNX gdb as it does not support path parameter for the MI call
const QByteArray command = m_isQnxGdb ? "run" : "-exec-run";
postCommand(command + " " + remoteExecutable.toLocal8Bit(), GdbEngine::RunRequest, CB(handleExecRun));
} else { } else {
notifyEngineRunAndInferiorStopOk(); notifyEngineRunAndInferiorStopOk();
continueInferiorInternal(); continueInferiorInternal();