Does existence of $HOME/.gdbinit interfere with debugging via VSCode cpptools extension?

[TryerGit]

Once a debug executable is created, at times I want to debug it from the command line using gdb directly instead of via VSCode. To enable this command line debugging, as suggested over at https://developers.redhat.com/articles/the-gdb-developers-gnu-debugger-tutorial-part-1-getting-started-with-the-debugger

I have a $HOME/.gdbinit file with settings/other gdb startup commands.

When debugging via VSCode cpptools extension (as opposed to directly via the command line gdb), is $HOME/.gdbinit file read? If yes, is there a way to disable that?

[Joel Town Road (hippi345)]

Yes, it's just a normal gdb --interpreter=mi so your home init file loads. Pass -nh through miDebuggerArgs to skip it in VS Code only:

"MIMode": "gdb",
"miDebuggerArgs": "-nh",

-nh skips ~/.gdbinit and ~/.config/gdb/gdbinit. -nx also skips the system one, which some distros use for pretty-printers, so -nh is usually what you want. Anything you do want can go in setupCommands. Stuff like GEF or gdb-dashboard is what usually breaks MI.