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
While working to verify debugging of remotely built Swift libraries, @adrian-prantl read through some types logs from my project and noted that the "-simulator" suffix was missing from the triple used by the SwiftASTContextForExpressions. I have verified this is reproducible on the latest dev snapshot (from 12/18/19).
From the LLDB types log, I can see that the SwiftASTContextForExpressions is using the wrong triple ("-simulator" is missing):
Download and unzip the attached Xcode project "AppShell".
Select the appropriate Swift toolchain in Xcode (I used dev snapshot from 12/18/19).
Set a breakpoint anywhere in AppDelegate.
Build and run the project.
When the breakpoint is hit, exec po self in the LLDB console.
Observe the LLDB types log.
About the sample project
This is an Xcode project that resembles the way an iOS app is created by Bazel. The only source code is contained in "AppLib", which is linked with the source-less target "AppShell". To closely simulate my build environment, I have also set the -no-serialize-debugging-options flag which may or may not be related.
The text was updated successfully, but these errors were encountered:
Just to clarify - debugging seems to work correctly and I'm able to evaluate expressions in the debug session. I'm unsure what internal info/data structures could be corrupted and whether it has some subtle or hard to see impact on debugging.
And that is also the last patch, because the final verdict on whether something is ios-simulator or not can only be made once we have a process, so it "behaves correctly" that we misidentify it in the per-module SwiftASTContext.
Attachment: Download
Additional Detail from JIRA
md5: f94c34d07829038be0b30d52e5a861dc
Issue Description:
While working to verify debugging of remotely built Swift libraries, @adrian-prantl read through some types logs from my project and noted that the "-simulator" suffix was missing from the triple used by the
SwiftASTContextForExpressions
. I have verified this is reproducible on the latest dev snapshot (from 12/18/19).From the LLDB types log, I can see that the
SwiftASTContextForExpressions
is using the wrong triple ("-simulator" is missing):From the same types log, other instances of
SwiftASTContext
are using the correct triple (contains "-simulator"):Steps to repro
Download and unzip the attached Xcode project "AppShell".
Select the appropriate Swift toolchain in Xcode (I used dev snapshot from 12/18/19).
Set a breakpoint anywhere in
AppDelegate
.Build and run the project.
When the breakpoint is hit, exec
po self
in the LLDB console.Observe the LLDB types log.
About the sample project
This is an Xcode project that resembles the way an iOS app is created by Bazel. The only source code is contained in "AppLib", which is linked with the source-less target "AppShell". To closely simulate my build environment, I have also set the
-no-serialize-debugging-options
flag which may or may not be related.The text was updated successfully, but these errors were encountered: