forked from llvm/llvm-project
-
Notifications
You must be signed in to change notification settings - Fork 103
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
[lldb] Backport D72880: "Fix a buffer-size bug when the first DW_OP_piece is undefined" #38
Closed
Closed
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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -2331,6 +2331,10 @@ bool DWARFExpression::Evaluate( | |
// not available. Fill with zeros for now by resizing the data and | ||
// appending it | ||
curr_piece.ResizeData(piece_byte_size); | ||
// Note that "0" is not a correct value for the unknown bits. | ||
// It would be better to also return a mask of valid bits together | ||
// with the expression result, so the debugger can print missing | ||
// members as "<optimized out>" or something. | ||
::memset(curr_piece.GetBuffer().GetBytes(), 0, piece_byte_size); | ||
pieces.AppendDataToHostBuffer(curr_piece); | ||
} else { | ||
|
@@ -2445,8 +2449,8 @@ bool DWARFExpression::Evaluate( | |
return false; | ||
} | ||
} | ||
op_piece_offset += piece_byte_size; | ||
} | ||
op_piece_offset += piece_byte_size; | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This is the fix, moving the offset update outside of the You can see the "then" arm above (handling undef pieces) because a comment was added to it. |
||
} | ||
} break; | ||
|
||
|
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.
This behavior of treating undef data as zeroed isn't ideal, but it should be fine for padding.