[lldb] Avoid mangling empty opaque types #10947
Open
+7
−0
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.
Update
TypeSystemSwiftTypeRef::RemangleAsType
to handle empty opaque types. Without this change, assertions will occur when running unit tests with an asserts-build of lldb.An example of where this happens is
Builtin.RawPointer
($sBpD
). For values with that type, the typeref is:When demangling the above typeref, the resulting demangle tree is an empty
OpaqueType
:In Swift's
Remangler::mangleOpaqueType
, it's expected that the opaque type have 3 children: