-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
Account for GetSyntheticValue failures
#155737
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
Merged
+30
−23
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Question (non-blocking): Trying to better understand the synthethic provider relationships. Do we know why dereferences are handled I guess "directly" by
DefaultSyntheticProvider, and not another*SyntheticProvider? Is it just because dereferences are very common?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DefaultSyntheticProvidershouldnt ever encounter pointer types at all anymore, and its pointer logic was vestigial. Due to this check, all indirection should go throughIndirectionSyntheticProvider.Having an indirection provider fixes a number of issues that boil down to "none of our providers expect pointers to be passed in". Usually it's fine because LLDB propogates pointee children upwards as pointer children, but when we're doing things like inspecting the type's layout directly (e.g. enum variants) or a type's generic params, looking at the pointer type causes the logic to fail.
There's an alternative, iirc it's a flag on synthetics/summaries called
lldb.eTypeOptionFrontendWantsDereference. I think it does what we want (forces only dereferenced/non-pointer entities passed to providers), but i need to test it and dig through the logic in LLDB to be sure.$$dereference$$is a special child name and LLDB uses it to allowoperator *dereferencing andoperator ->field access in the repl.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the detailed reply