-
Notifications
You must be signed in to change notification settings - Fork 54
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
[BUG]: Symbol resolution for /linker
in Android 15
#63
Comments
The best approach would be completely removing SO list hiding as it's just more of a workaround to a bigger problem, I'll investigate to see the next step. Thank you. |
You commit 5b5c2f has fixed the issue. Here are the logs for your information: |
This commit improves how the symbols like solist are searched. This allows to phones that have linker64 with symbols with llvm suffix to still have maps hiding. closes #63
I may add that there are Android 15 devices that seem to not have that llvm sufix, however the made PR should fix in any case. |
Solist hiding is surely needed. Current method using We should drop those libraries in the SoList |
/linker
in Android 15/linker
in Android 15
Alternatively, one could use |
On Android 15+ in some devices, the symbol names of some static variables such as `solist`, has a `llvm` suffix in its exported name. Current commit handles this case and close PerformanC#63 as fixed. Co-authored-by: ThePedroo <[email protected]>
Version
v1.0.0 (234-f1ba34f-debug)
Modules
Zygisk - LSPosed by JingMatrix v1.10.1 (7118)
Description
In Android 15, the symbols
__dl__ZL6solist
,__dl__ZL6somain
and__dl__ZL4vdso
are no longer present, so thatSoList::Initialize()
always fails.Indeed they are replaced by names like
__dl__ZL6solist.llvm.7690929523238822858
and so on.I update the
readelf
output oflinker64
binary as evidencelinker_readelf.txt
Steps to reproduce
[ 2024-10-19T20:53:12.823 1000: 1586: 1586 E/zygisk-core64 ] Failed to initialize SoList
Logs
Here is the LSPosed log:
verbose_2024-10-19T20:53:12.156478.log
Confirmations
Code of Conduct
The text was updated successfully, but these errors were encountered: