Open
Conversation
Contributor
|
Seems may have some implications on behavior Hopefully positive ones, as currently symbol sizes aren't as ideal as they could be. I'm guessing addition of size determinations in object crate does mean a refactor later along the line since until now objdiff handled that. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bumping object crate to version 0.39.0
I ran into a strange issue with a custom generated ARM object file that had data that wasn't aligned to an expected value. The object crate was fussy about it and it's now been resolved.
See the following issue and commits
gimli-rs/object#848
gimli-rs/object#861