Don't parse ranges for partial units #313
Merged
Conversation
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
These don't normally have ranges anyway, but it is possible for them to have a DW_AT_stmt_list that points to the same program that contains ranges for a compilation unit, and loading the ranges from that is wrong. This used to work because our search would find the compilation unit first, but we changed the search order and now it was finding the partial unit.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
These don't normally have ranges anyway, but it is possible for them to have a DW_AT_stmt_list that points to the same program that contains ranges for a compilation unit, and loading the ranges from that is wrong.
This used to work because our search would find the compilation unit first, but we changed the search order and now it was finding the partial unit.
Closes #311