Error when running lldb debugger from bottom toolbar

Brief Issue Summary

When clicking on ‘Debug’ from the bottom toolbar the lldb debugger fails to start with an error in the debug console. Pressing F5 however, will launch the debugger correctly.

Expected Behavior

This used to work in previous versions.

CMake Tools Log

DEBUG CONSOLE log:

Starting: “/usr/bin/lldb” --interpreter=mi lldb: unrecognized option `–interpreter=mi’ error: unknown or ambiguous option Usage: …

Platform and Versions

• Operating System: macOS 10.12.6
• CMake Version: 3.20.2
• VSCode Version: 1.25.1
• CMake Tools Extension Version: 1.1.1
• Compiler/Toolchain: clang 9.0.0

Other Notes/Information

launch.json: “version”: “0.2.0”, “configurations”: [ { “name”: “(lldb) Launch”, “type”: “cppdbg”, “request”: “launch”, “program”: “${workspaceFolder}/service/app”, “args”: [], “stopAtEntry”: false, “cwd”: “${workspaceFolder}/service”, “environment”: [], “externalConsole”: false, “MIMode”: “lldb”, } ]

$ lldb --version lldb-900.0.64 Swift-4.0

[FelikZ]

@vector-of-bool hi, 1.1.3 does not solve it automatically for me. I am using this workaround at the moment:

    "cmake.debugConfig": {
        "stopAtEntry": false,
        "MIMode": "lldb",
        "miDebuggerPath": "/Users/felikz/.vscode/extensions/ms-vscode.cpptools-0.20.1/debugAdapters/lldb/bin/lldb-mi",
        "logging": {
                "trace": true,
                "engineLogging": true,
                "traceResponse": true
        }
    },

[rnorton1]

Wouldnt you ultimately want to integrate it with the existing launch system configuration(s) rather than generating your own on the fly? Or as a quick fix, maybe you could take a stab at the debugger from the compiler being used?

The debugger on the tool bar is a nice feature. I think it would be worth expanding on to cater for all configurations.