[lldb] Print ValueObject when GetObjectDescription fails (#152417)#11178
Merged
kastiglione merged 2 commits intoSep 17, 2025
Merged
Conversation
Author
|
@swift-ci test |
e6ff6e7 to
a9df4d9
Compare
Author
|
@swift-ci test |
a9df4d9 to
52281c1
Compare
This fixes a few bugs, effectively through a fallback to `p` when `po` fails. The motivating bug this fixes is when an error within the compiler causes `po` to fail. Previously when that happened, only its value (typically an object's address) was printed – and problematically, no compiler diagnostics were shown. With this change, compiler diagnostics are shown, _and_ the object is fully printed (ie `p`). Another bug this fixes is when `po` is used on a type that doesn't provide an object description (such as a struct). Again, the normal `ValueObject` printing is used. Additionally, this also improves how lldb handles an object description method that fails in some way. Now an error will be shown (it wasn't before), and the value will be printed normally. (cherry picked from commit ae7e1b8)
52281c1 to
12405a2
Compare
Author
|
rebased to stable/21.x |
Author
|
@swift-ci test |
1 similar comment
Author
|
@swift-ci test |
Author
|
@swift-ci test macOS |
3 similar comments
Author
|
@swift-ci test macOS |
Author
|
@swift-ci test macOS |
Author
|
@swift-ci test macOS |
adrian-prantl
pushed a commit
to adrian-prantl/llvm-project
that referenced
this pull request
Dec 12, 2025
swiftlang#11178) * [lldb] Print ValueObject when GetObjectDescription fails (llvm#152417) This fixes a few bugs, effectively through a fallback to `p` when `po` fails. The motivating bug this fixes is when an error within the compiler causes `po` to fail. Previously when that happened, only its value (typically an object's address) was printed – and problematically, no compiler diagnostics were shown. With this change, compiler diagnostics are shown, _and_ the object is fully printed (ie `p`). Another bug this fixes is when `po` is used on a type that doesn't provide an object description (such as a struct). Again, the normal `ValueObject` printing is used. Additionally, this also improves how lldb handles an object description method that fails in some way. Now an error will be shown (it wasn't before), and the value will be printed normally. (cherry picked from commit ae7e1b8) * fix TestSwiftExpressionErrorReporting (cherry picked from commit e67aa08)
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This fixes a few bugs, effectively through a fallback to
pwhenpofails.The motivating bug this fixes is when an error within the compiler causes
poto fail.Previously when that happened, only its value (typically an object's address) was
printed – and problematically, no compiler diagnostics were shown. With this change,
compiler diagnostics are shown, and the object is fully printed (ie
p).Another bug this fixes is when
pois used on a type that doesn't provide an objectdescription (such as a struct). Again, the normal
ValueObjectprinting is used.Additionally, this also improves how lldb handles an object description method that
fails in some way. Now an error will be shown (it wasn't before), and the value will be
printed normally.
(cherry picked from commit ae7e1b8)
rdar://134291640
rdar://134520818