and got further on my bughunt. You might want to think if a similar regex as for clang.
(As a sidenote, it seems that when using a toolchain file with CMake, the CMAKE_<lang>_COMPILER variables don't necessarily end up in CMakeCache.txt so this method of auto-detection based on the cache fails to begin with...)
I don't have any experience in developing VS Code extensions so I don't even try to make a proper patch, but I found out that here:
https://github.com/microsoft/vscode-cmake-tools/blob/406216a5309d5d5997b8567c0fb98c04bbf563e2/src/debugger.ts#L219
the
compilerPath.replace
operation is using a clang-specific regex. In my localdist/main.js
I replaced this line with:miDebuggerPath = compilerPath.replace('gcc', 'gdb').replace('g++', 'gdb');
and got further on my bughunt. You might want to think if a similar regex as for clang.
(As a sidenote, it seems that when using a toolchain file with CMake, the
CMAKE_<lang>_COMPILER
variables don't necessarily end up inCMakeCache.txt
so this method of auto-detection based on the cache fails to begin with...)