Open peterkos opened 10 months ago
The "symptom" here was hitting breakpoints, but unable to print any vars in the console, and the callstack was obfuscated, like so:
s18SKSwiftPMWorkspace05SwiftB0C3url17toolchainRegistry10buildSetupACSg10Foundation3URLV_6SKCore09ToolchainF0CAK05BuildH0VtcfC
Attempting to print a var would yield this fun error, informing us (tldr) that lldb
wasn't loaded, + we're runnin' only the debug symbols from the executable:
:po buildSetup
error: Could not find type system for language swift: TypeSystem for language swift doesn't exist
Does lldb.library
in the configuration work in vsocde? I was under the impression that was a workspace setting similar to Debugger.sublime-preferences
.
There currently isn't a great place to add notes for specific adapters besides the readme
Morning!
I was struggling to attach
lldb
to a SwiftPM-built project (sourcekit-lsp
, of course) with the following config:(Opting for
A
over the/Current/
symlink, and targeting the macos SPM debug output)After much hoopla, I found a teeny little setting in
Debugger.sublime-settings
that overrides the debugger configurations!https://github.com/daveleroy/SublimeDebugger/blob/95b7098d6d432e38b847bd1d42c525186e4e64f8/Debugger.sublime-settings#L57-L58
In fact --
codelldb
, contrary to its Swift documentation, doesn't need to havelldb.library
set in this case, because of this setting. Nor does it needLLDB_DEBUGSERVER_PATH
as alldb.launch.env
😅Working config:
Maybe a callout in the README for this setting would be helpful? I'd normally throw it in
codelldb
, but that's VSCode specific :eyes: Happy to add one wherever!