forked from qt-creator/qt-creator
Fix debug start for VxWorks
The VxWorks plugin sets the target extended-remote in the commands after connect, so there is no need to call target again. Change-Id: I8c35315f812a6ea3b0b3da76e3a6c9bcc130edf3 Reviewed-by: hjk <hjk@qt.io> Reviewed-by: Jarek Kobus <jaroslaw.kobus@qt.io>
This commit is contained in:
@@ -4623,8 +4623,10 @@ void GdbEngine::runEngine()
|
|||||||
|
|
||||||
claimInitialBreakpoints();
|
claimInitialBreakpoints();
|
||||||
notifyEngineRunAndInferiorStopOk();
|
notifyEngineRunAndInferiorStopOk();
|
||||||
|
// in case of vxworks target remote is already set by commandsAfterConnect
|
||||||
runCommand({"target remote " + extractRemoteChannel(rp.remoteChannel(), rp.remoteChannelPipe())});
|
if (!rp.debugger().command.executable().contains("gdb_bin"))
|
||||||
|
runCommand({"target remote " + extractRemoteChannel(rp.remoteChannel(),
|
||||||
|
rp.remoteChannelPipe())});
|
||||||
|
|
||||||
} else if (runParameters().isLocalAttachEngine()) {
|
} else if (runParameters().isLocalAttachEngine()) {
|
||||||
|
|
||||||
|
Reference in New Issue
Block a user