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
After cleaning the caches/derived data and running a new build the problem returned to appear. My limited knowledge about swift and lldb integration doesn't let me figure out what's different between those two cases.
The app codebase is Swift with some pre-built third-party libs (swift, obj-c, c++). To deal with Buck relative paths and be able to set breakpoints we're using some settings set target.source-map.
We're not generating dsym files to debug, only using object files embedded DWARF (only generating dsyms to symbolicate crashes). But, by generating dsym files we're getting a different error output:
(lldb) poself.customViewerror: Couldn't lookup symbols: direct field offset for SomeCoolModulePresentation.CoolMenuViewController.customView : SomeCoolModulePresentation.CoolMenuViewProtocol
A sample project that reproduces the issue is available here
The text was updated successfully, but these errors were encountered:
Environment
Xcode 13 | Apple Swift version 5.5 (swiftlang-1300.0.31.1 clang-1300.0.29.1)
macOS BigSur
Additional Detail from JIRA
md5: 0d8ab96f9e0821fda8683b3779febed0
Issue Description:
Related to Intermittent behavior while debugging swift application with LLDB
We use Buck as our swift application build system and we are getting some intermittent behaviors while debugging the app with LLDB.
When stopping at some breakpoints and running a
po
with some instance value of self we're getting this:Searching for some more information about the error with
log enable lldb types expr
that's what I get for this case:After some clean builds with no change in the codebase or build process, finally get some successful response:
Lldb types expr log:
After cleaning the caches/derived data and running a new build the problem returned to appear. My limited knowledge about swift and lldb integration doesn't let me figure out what's different between those two cases.
The app codebase is Swift with some pre-built third-party libs (swift, obj-c, c++). To deal with Buck relative paths and be able to set breakpoints we're using some
settings set target.source-map
.We're not generating dsym files to debug, only using object files embedded DWARF (only generating dsyms to symbolicate crashes). But, by generating dsym files we're getting a different error output:
A sample project that reproduces the issue is available here
The text was updated successfully, but these errors were encountered: