feat(elf_util): Added Step 3(r--p) fallback lookup mechanism .Fix the problem that the address cannot be obtained on Android 10 #497
Conversation
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
…d 10) - When the Step 2 (r-xp) mode is not found, implement the lookup logic to fall back to the first r--p segment - On android 10 Step 1 to Step 2 doesn't match any pattern, but r--p does have a libart.so address - Log findModuleBase(): Found 4 filtered map entries for libart.so: findModuleBase(): 0x70991e8000 r--p /apex/com.android.runtime/lib64/libart.so findModuleBase(): 0x7099327000 --xp /apex/com.android.runtime/lib64/libart.so findModuleBase(): 0x70997de000 rw-p /apex/com.android.runtime/lib64/libart.so findModuleBase(): 0x70997e1000 r--p /apex/com.android.runtime/lib64/libart.so findModuleBase(): `r--p` -> `r-xp` pattern not found. Falling back to first `r-xp` entry. findModuleBase(): `r-xp` pattern not found. Falling back to first `r--p` entry. findModuleBase(): Found first `r--p` block at 0x70991e8000 findModuleBase(): get module base /apex/com.android.runtime/lib64/libart.so: 0x70991e8000 findModuleBase(): update path: /apex/com.android.runtime/lib64/libart.so
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When the Step 2 (r-xp) mode is not found, implement the lookup logic to fall back to the first r--p segment
On android 10 Step 1 to Step 2 doesn't match any pattern, but r--p does have a libart.so address
Log findModuleBase(): Found 4 filtered map entries for libart.so:
findModuleBase(): 0x70991e8000 r--p /apex/com.android.runtime/lib64/libart.so
findModuleBase(): 0x7099327000 --xp /apex/com.android.runtime/lib64/libart.so
findModuleBase(): 0x70997de000 rw-p /apex/com.android.runtime/lib64/libart.so
findModuleBase(): 0x70997e1000 r--p /apex/com.android.runtime/lib64/libart.so
findModuleBase():
r--p->r-xppattern not found. Falling back to firstr-xpentry.findModuleBase():
r-xppattern not found. Falling back to firstr--pentry.findModuleBase(): Found first
r--pblock at 0x70991e8000findModuleBase(): get module base /apex/com.android.runtime/lib64/libart.so: 0x70991e8000
findModuleBase(): update path: /apex/com.android.runtime/lib64/libart.so