Pierson Lee

@ivankravets Please post your launch.json. If you set `cwd`, we set it to that value. If you want to call a different gdb instead of `/usr/bin/gdb` you can specify `"miDebuggerPath"`...

@ivankravets From my understanding, 'gdb' uses `-environment-cd` command to set that. If you look at: https://sourceware.org/gdb/onlinedocs/gdb/GDB_002fMI-Program-Context.html and search for `-environment-cd` it tells me that the command will set the working...

@ivankravets We use "MI Interpreter mode" to talk to our debuggers. Based on the mode we support, the correct way of setting the working directory was `-environment-cd` command. We added...

@ivankravets The reason this has not been resolved is we are unsure what would happen to the working scenarios if this change were made. You can work around this by...

@ivankravets We added that message because people did not know that the debugger executable needed to be signed and some platforms, the OS does not allow debug/attaching to another process...

>I feel like the signing issue here is orthogonal to the cwd issue. We should probably open a new issue on that. I'm guessing we would enforce signing on mac...

@snahmad we aren't the extension that provides `"type": "gdb"`. Please check your installed extensions and contact that extension owner. Our extension provides `"type": "cppdbg"`.

You need to go to your VS Code install, go to the extensions page and identify it. My search on the [VS Code Extension Gallery](https://marketplace.visualstudio.com/search?term=gdb&target=VSCode&category=All%20categories&sortBy=Relevance) brings up a few options

>Tried adding logging to debugger but no events are being captured for this What did you try? Can you please post your `launch.json` and which type of application you are...

@simon-p-r I have your repo but I can't figure out how to build. I installed your tool set items below and then ran `vcpkg install libuv`, I set the libuv...