Skip to content

[lldb] Make ReadCStringFromMemory default to read from the file-cache. #3856

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

Conversation

augusto2112
Copy link

Differential Revision: https://reviews.llvm.org/D118265

(cherry picked from commit b414954)

@augusto2112
Copy link
Author

@swift-ci test

@augusto2112
Copy link
Author

@swift-ci test macOS

Now that reading C strings go through the file-cache by default, make
sure that any calls that come from LLDBMemoryReader force live memory
when we can't read from the file-cache. This is the case when:
- The LLDB setting marks it as disabled.
- The target is 32 bits (this may be subject to change).
- The address we're reading from is not one of the fake addresses we
  resolved in LLDBMemoryReader.
@augusto2112 augusto2112 force-pushed the read-cstrings-from-filecache-cherry-pick branch from f25c176 to 03a0435 Compare February 1, 2022 12:53
@augusto2112
Copy link
Author

Besides the cherry-pick, I added a second commit so we don't read from the file-cache when we didn't resolve the address ourselves:

[lldb] Force live memory if we can't read from the file-cache

Now that reading C strings go through the file-cache by default, make
sure that any calls that come from LLDBMemoryReader force live memory
when we can't read from the file-cache. This is the case when:
- The LLDB setting marks it as disabled.
- The target is 32 bits (this may be subject to change).
- The address we're reading from is not one of the fake addresses we
  resolved in LLDBMemoryReader.

@augusto2112
Copy link
Author

@swift-ci test

@augusto2112
Copy link
Author

@swift-ci test macOS

@augusto2112 augusto2112 merged commit 0412b03 into swiftlang:stable/20211026 Feb 3, 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.

2 participants