You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In fact -- codelldb, contrary to its Swift documentation, doesn't need to have lldb.library set in this case, because of this setting. Nor does it need LLDB_DEBUGSERVER_PATH as a lldb.launch.env 😅
Maybe a callout in the README for this setting would be helpful? I'd normally throw it in codelldb, but that's VSCode specific 👀 Happy to add one wherever!
The text was updated successfully, but these errors were encountered:
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!SublimeDebugger/Debugger.sublime-settings
Lines 57 to 58 in 95b7098
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 👀 Happy to add one wherever!The text was updated successfully, but these errors were encountered: