-
Notifications
You must be signed in to change notification settings - Fork 15.4k
[lldb] Add DWARFExpressionEntry and GetExpressionEntryAtAddress() to … #144238
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
JDevlieghere
merged 15 commits into
llvm:main
from
UltimateForce21:add-dwarfexprentry-api
Jul 12, 2025
Merged
Changes from 14 commits
Commits
Show all changes
15 commits
Select commit
Hold shift + click to select a range
8ed8c54
[lldb] Add DWARFExpressionEntry and GetExpressionEntryAtAddress() to …
UltimateForce21 1db5002
Update lldb/include/lldb/Expression/DWARFExpressionList.h
UltimateForce21 a26010b
Update lldb/include/lldb/Expression/DWARFExpressionList.h
UltimateForce21 72237b7
Update lldb/source/Expression/DWARFExpressionList.cpp
UltimateForce21 94e4951
Update DWARFExpressionList.h
UltimateForce21 e8142da
Update DWARFExpressionList.cpp
UltimateForce21 7e8741e
Update DWARFExpressionList.h
UltimateForce21 c4cd77f
Update DWARFExpressionList.cpp
UltimateForce21 62c02a9
Change GetExpressionEntryAtAddress to return std::optional instead of…
UltimateForce21 d015971
Update DWARFExpressionList.cpp
UltimateForce21 60898ea
Add underflow/overflow checks to GetExpressionEntryAtAddressi
UltimateForce21 3462165
Make file_range optional in DWARFExpressionEntry for always-valid expr
UltimateForce21 c01a747
Merge branch 'main' into add-dwarfexprentry-api
UltimateForce21 ec3ac93
Merge branch 'main' into add-dwarfexprentry-api
UltimateForce21 38baa90
Fixed formating issues
UltimateForce21 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
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.
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.
Out of curiosity: Do we still need this API, or is it just a subset of the function above?
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.
As you know the new function GetExpressionEntryAtAddress, does almost exact same thing as this one. I don't see this function being used anywhere else in the lldb code base, so maybe it can be removed, but to be safe I did not want to alter it. But from what I can tell, it should be okay to remove it. We can also choose to keep it and maybe refactor it to just call the GetExpressionEntryAtAddress and just return the
DWARFExpression *expr.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.
If it's completely unused, and there is no indication that was added in support of any downstream clients (either as a comment or in the commit message) we could consider deleting it in a separate PR. Not urgent.