[lldb] Handle unsupported type in GetPointerType #4975
Merged
+0
−0
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
(cherry-picked from commit 21d1b51)
|
@swift-ci test |
kastiglione
deleted the
lldb-Handle-unsupported-type-in-GetPointerType-4954-stable-20220421
branch
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.
For
TypeSystemSwiftTypeRef::GetPointerTypeto succeed, the given type variable first must be demangled. If that fails, the function must return an emptyCompilerType.This fixes downstream crashes in
GetPointerTowhereNode::addChildis called, but with a null node. This causes an abort inaddChild, where the child node is required to be non-null.rdar://96170947
(cherry-picked from commit 21d1b51)