[5.9][Macros] Serialize plugin search paths for LLDB use #65616
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rdar://107030743
|
@swift-ci Please test |
adrian-prantl
approved these changes
May 3, 2023
fredriss
approved these changes
May 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Write down the plugin search paths in the binary swiftmodule files so LLDB can load them and understand the macros in the expression evaluator. This may list local search paths as expected for debugging locally built modules, however LLDB may want to ignore these paths when read from a distributed swiftmodule file.
Risk: Low, the information will only be read by LLDB. There's no need to bump the swiftmodule format version.
Scope: Macro support in LLDB.
Reviewer: @rintaro
rdar://107030743
Cherry-pick of #65370.