lldb: -- Could not find swift-plugin-server for C:\Users\compnerd\AppData\Local\Programs\Swift\Toolchains\6.0.1+Asserts\usr\bin

[compnerd]

Description

When using LLDB from the command line, evaluating expressions yields the following diagnostic message:

-- Could not find swift-plugin-server for C:\Users\compnerd\AppData\Local\Programs\Swift\Toolchains\6.0.1+Asserts\usr\bin

Reproduction

p var

Expected behavior

The plugin server to be found

Environment

> swiftc -version
Swift version 6.0.1 (swift-6.0.1-RELEASE)
Target: aarch64-unknown-windows-msvc

Additional information

No response

[adrian-prantl]

This is probably not a bug. The compiler adds plugin search paths by default that don't necessarily exist.

[adrian-prantl]

You're probably seeing this because it gets sent to the always-on log channel.

[compnerd]

This really makes the debugger less functional IMO, we should ignore these warnings in LLDB then I think.

[adrian-prantl]

This really makes the debugger less functional IMO, we should ignore these warnings in LLDB then I think.

Can you be more specific?
Are you arguing against the always-on log channel in LLDB on Windows being routed to stderr, or something else?

[compnerd]

I think that we should filter out the warnings. stderr is visible on the console and does interfere with usability. As an example, this is what happens when you try to do expression evaluation:

I'd like to make the LLDB experience on Windows at least usable (the overall experience feels pretty rough in comparison to WinDBG still).