macOS: Debugger doesn't work for VSCode

[zaneenders]

Problem

After installing Swiftly 1.0 and switching VSCode to using that toolchain under settings.

// settings.json file
"swift.path": "/Users/zane/.swiftly/bin",

The debugger throws the above error. The following code with a breakpoint on #expect(true) triggers the error.

import Testing
@testable import Example

@Test func example() async throws {
    #expect(true)
    // Write your test here and use APIs like `#expect(...)` to check expected conditions.
}

Console.app has the following errors.

Could be related to swiftlang/swift-package-manager#7994

Using XCode's toolchain debugging works correctly.

/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/swift

Thanks,
Zane

[adam-fowler]

I'm guessing the debugserver doesn't like applications called swiftly attaching to it. If you point directly to the installed swift toolchain using the Select Toolchain.... command it works fine.

Including @plemarquand as he may have some thoughts

[plemarquand]

Hi Zane, thanks for the report.

I think you're right in that this is swiftlang/swift-package-manager#7994, but to know for sure I'd need to know what toolchain you're using with Swiftly.

That said, I attempted to debug using the released 6.0.3 toolchain proxying through Swiftly as you have and was able to debug without issue, which makes me think the specific toolchain you have installed still suffers from swiftlang/swift-package-manager#7994.

However its important to note that the VS Code Swift extension hasn't yet been updated to be fully compatible with the newly released Swiftly for macOS. The extension will search for some toolchain executables with xcrun --find swift, and xcrun will always look in the toolchain for the active Xcode. This means you may run in to issues using Swiftly on macOS if your Xcode has a different version of the toolchain being managed by Swiftly. I have a draft PR up to fix this, but it wont be available until the next release.

[zaneenders]

Thanks for helping me out. I tried with both 6.0.3 and main-snapshot.

Reinstalled swiftly this morning.

➜  ~ which swift
/Users/zane/.swiftly/bin/swift
➜  ~ swift --version
Apple Swift version 6.0.3 (swift-6.0.3-RELEASE)
Target: arm64-apple-macosx15.0
➜  ~ 

I gave Select Toolchain... a try and it resulted in the same error.

Everything seems to be building correctly using swiftly though..

VSCode "terminal" output for swift: Build All

/Users/zane/.swiftly/bin/swift build --build-tests -Xswiftc -diagnostic-style=llvm

How did you setup the proxy, so I may try that?

aside: Would it be worth trying to add a swiftly self-uninstall command?

[plemarquand]

Does a 6.0.3 version show up in the list of available toolchains that points to ~/Library/Developer/Toolchains instead of the swiftly proxy bin dir? You may have better luck picking that toolchain instead until macOS swiftly support lands.

[plemarquand]

You could also try removing all references to swift.path from your settings.json and let the PATH handle finding the swiftly proxy. That's how I had debugging working.