From 495c361ea0810066db53d37863596827baab1e56 Mon Sep 17 00:00:00 2001 From: Karim Pinter Date: Tue, 22 Apr 2025 16:03:06 +0300 Subject: [PATCH] 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 Reviewed-by: Jarek Kobus --- src/plugins/debugger/gdb/gdbengine.cpp | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/src/plugins/debugger/gdb/gdbengine.cpp b/src/plugins/debugger/gdb/gdbengine.cpp index f2d323c69ba..152bf8702a3 100644 --- a/src/plugins/debugger/gdb/gdbengine.cpp +++ b/src/plugins/debugger/gdb/gdbengine.cpp @@ -4623,8 +4623,10 @@ void GdbEngine::runEngine() claimInitialBreakpoints(); notifyEngineRunAndInferiorStopOk(); - - runCommand({"target remote " + extractRemoteChannel(rp.remoteChannel(), rp.remoteChannelPipe())}); + // in case of vxworks target remote is already set by commandsAfterConnect + if (!rp.debugger().command.executable().contains("gdb_bin")) + runCommand({"target remote " + extractRemoteChannel(rp.remoteChannel(), + rp.remoteChannelPipe())}); } else if (runParameters().isLocalAttachEngine()) {