Add vdex021 support #52
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
|
@IgorEisberg thank you for submitting the PR and sorry for sitting on it for such a long time. I'll check the changes in vdex 021 dropped with Android 10 and verify if optimal to merge your patch and add missing changes in parser or refactor a few bits with a different strategy. |
UncleSugar
approved these changes
Nov 13, 2019
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.
Had to make some renaming in 019 files to be able to compile 021 without conflicting duplicates.
This basically reads the extra data added in vdex021's header:
uint32_t bootclasspath_checksums_size_;
uint32_t class_loader_context_size_;
However, currently, the extra data at the end of the file isn't parsed, but at least it allowed the extracting of the contained cdex files, as they don't seem to be directly related to that extra data.