GDB's working directory doesn't match launch location

[AE1020]

I noticed this at first when I set did set logging on in the startup commands, and found gdb.txt in the directory vscode was launched from... not alongside the executable.

I tried hardcoding a cd command into the generation of the gdb launch, here:

vgdb/src/debuggers/gdb/GDB.ts

Line 775 in 3eff76c

return `bash -c "${this.createEnvironmentVariablesSetterCommand()} trap '' 2 ; ${

So just doing cd /path/to/debuggee/ ; at the beginning of the executed string, before the $.

When I did that, it not only put gdb.txt in a better place, but made other things work that weren't. I'd been getting messages from gdb of "No source file named..." on paths that did exist. But it turns out that message really means "Couldn't find symbols for file named...". By launching gdb in the directory where the output executable was (instead of where vscode was launched) these errors went away.

After doing this I was able to debug chromium built from source. And vgdb does not seem to have problems watching Blink::Node variables (which causes vscode-cpptools to hang),

[penagos]

If you have a patch for this I'd be more than happy to merge it into the master branch and queue it for the next bug fix release.

[AE1020]

All I did was hardcode a cd to the directory I was working with at the head of the invocation.

Doing it correctly you'd have to decide where to get this directory:

• the directory of the executable being debugged?
• the cwd property from the launch.json file?
• some independent overridable property?

Then there is the question of defaulting (if there's no cwd, then should it fall back to the executable's directory?)