Skip to content

[lldb/Process] Silence toolchain mismatch warnings for Scripted Processes (NFC) #4068

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 17, 2022

Conversation

medismailben
Copy link

@medismailben medismailben commented Mar 15, 2022

When using Scripted Processes, it's very likely that lldb's version
might not align with the swift compiler that built the target.

Thus, this will cause the toolchain mismatch warnings to be shown to the
user every time they "stop" in a Swift frame.

Since we shouldn't need Swift's AST to symbolicate the stopped stackframe,
we can safely silence these warnings for Scripted Processes.

Signed-off-by: Med Ismail Bennani [email protected]

@medismailben
Copy link
Author

Stable branch PR #4067

…sses (NFC)

When using Scripted Processes, it's very likely that lldb's version
might not align with the swift compiler that built the target.

Thus, this will cause the toolchain mismatch warnings to be shown to the
user every time they "stop" in a Swift frame.

Since we shouldn't need Swift's AST to symbolicate the stopped stackframe,
we can safely silence these warnings for Scripted Processes.

Signed-off-by: Med Ismail Bennani <[email protected]>
@medismailben medismailben force-pushed the silence-sp-warnings-next branch 2 times, most recently from 932ae2d to f68c4c4 Compare March 17, 2022 04:32
@medismailben medismailben merged commit 51b3ffa into swiftlang:next Mar 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant