Prevent file-exec-and-symbols step #11855
Replies: 2 comments 4 replies
|
Use "request": "launch" with "customLaunchSetupCommands": [] https://code.visualstudio.com/docs/cpp/launch-json-reference#_customlaunchsetupcommands With this configuration, the extension is running in "launch" mode and it will kill the process if you STOP the debugger. Instead, use "-exec detach" in the debug console. It would be great if they add a "customAttachSetupCommands" or something like that... |
0 replies
|
Thanks for the heads up 👍 {
name: "GDB attach",
type: "cppdbg",
request: "attach",
miDebuggerPath: bin,
MIMode: "gdb",
useExtendedRemote: true,
setupCommands: [
{ text: `target extended-remote ${address}` },
{ text: `source ${script_path}` },
],
program: debugLine[1],
processId: +debugLine[2],
}And it work like a charm ! |
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm currently trying to connect VSCode to a running (and executing) GDB server,
So I don't want any
execstep executed by VSCode.here is my launch.json
Despite my attempts with
launchCompleteCommand:NoneandstopAtConnect: true, VSCode tries to run a file-exec-and-symbols which fail in my environement.I also tried a "request:lauch" kind of run, which get stuck without any logs.
How to prevent this unwanted command to be run by VSCode GDB Client ?
All reactions