launch.json selects the incorrect debugger executable.

Brief Issue Summary

On my computer I have many different GCC installations, I have many LLVM installations etc…

When using the launch.json example here, the incorrect dbgExe is selected.

Expected:

Expected behaviour, Cmake Tools select the correct debugger, the same one used if launched using the CMake Tools dedicated debug button.

Apparent Behavior:

The resulting error is this:

However the compiler is this:

[cmake] -- Detecting C compiler ABI info
[cmake] -- Detecting C compiler ABI info - done
[cmake] -- Check for working C compiler: C:/utils/bin/mingw64/bin/clang.exe - skipped
[cmake] -- Detecting C compile features
[cmake] -- Detecting C compile features - done
[cmake] -- Detecting CXX compiler ABI info
[cmake] -- Detecting CXX compiler ABI info - done
[cmake] -- Check for working CXX compiler: C:/utils/bin/mingw64/bin/clang++.exe - skipped

Platform and Versions

• Operating System: Windows
• CMake Version: cmake version 3.19.0-rc3
• VSCode Version: 1.55.2
• CMake Tools Extension Version: 1.7.7
• Compiler/Toolchain: Clang 11.1.0

Other Notes/Information

I use clang from winlibs: http://www.winlibs.com/

My exact configuration in launch.json:

        {
            "name": "Launch",
            "type": "cppdbg",
            "request": "launch",
            "program": "${command:cmake.launchTargetPath}",
            "args": [],
            "stopAtEntry": true,
            "cwd": "${workspaceFolder}",
            "environment": [
                {
                    "name": "PATH",
                    "value": "$PATH:${command:cmake.getLaunchTargetDirectory}"
                }
            ],
            "setupCommands": [
                {
                    "description": "Enable pretty-printing for gdb",
                    "text": "-enable-pretty-printing",
                    "ignoreFailures": true
                }
            ]
        }

[seppeon]

Fair enough, in that case is there anything like: ${command:cmake.debuggerPath}

That can be used to work around the difference?

[WardenGnaw]

The difference is because the type": "cppdbg" in launch.json uses the debug adapter from Microsoft C/C++ Extension. It only uses the values defined in the launch.json. It will try its best to fill in the missing files, E.g. miDebuggerPath based on PATH.

The CMake extension extends on top of the Microsoft C/C++ Extension and their debug button provides the additional configuration fields to C/C++ Extension Debug Adapter.