Fix endianness issues in macho module #2041
Merged
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.
This is a backward incompatible change that affects the
macho.magic
field. After this change the value in themagic
field looks exactly as it looks in the file regardless of the endianness of the current platform, if the file starts withCA FE BA BE
the value in magic is0xCAFEBABE
, not0xBEBAFECA
as it used to be in little-endian architectures.Before this change, the
magic
value inconsistent between platforms with different endianness.