vscode-cmake-tools: 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

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 22 (8 by maintainers)

Most upvoted comments

@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
        }
    },

+21

FelikZ on Dec 11, 2018

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.

rnorton1 on Aug 6, 2018

The debug button in the bottom toolbar generates its own launch.json config on-the fly to run the debugger. It won’t use lldb or any settings you’ve provided in your launch.json. You probably want to use the launch.json integration to use F5 to debug your app with the CMake smarts. Read about that here.

vector-of-bool on Aug 2, 2018

No its still the same issue in 1.1.3:

Unable to start debugging. Unable to establish a connection to LLDB. The following message was written to stderr:

lldb: unrecognized option `--interpreter=mi'
error: unknown or ambiguous option

Still need to use the launch.json instead of the Debug button.

rnorton1 on Dec 3, 2018

You can still use the LLDB debugger. You just cant use it (at the moment) through the cmake-tools menu bar at the bottom. Set up a launch configuration (Debug -> Add Configuration) like the one in the OP. Then hit ‘F5’ key when you want to debug.

vector-of-bool seemed to be saying he will fix it from the cmake-tools menu bar by using these launch configuration profiles in the future.

rnorton1 on Aug 21, 2018