Skip to content
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

read: ignore tombstone entries in range and location lists #631

Merged
merged 3 commits into from Nov 3, 2022

Conversation

philipc
Copy link
Collaborator

@philipc philipc commented Oct 29, 2022

Fixes #629
cc @shuoli84

philipc and others added 3 commits October 29, 2022 13:40
Provide access to the raw range or location that is read
by the iterator, instead of parsing the list twice.
This means that dwarfdump doesn't need to match the parsing
logic of the iterator in order to figure out which
range/location is associated with a raw range/location.
Co-authored-by: shuo <shuoli84@gmail.com>
@philipc philipc merged commit e827f98 into gimli-rs:master Nov 3, 2022
@philipc philipc deleted the issue-629 branch November 3, 2022 03:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Invalid ranges read from wasm file
1 participant