br0kenpixel/ReZygisk
1
0
Fork 0
mirror of https://github.com/PerformanC/ReZygisk.git synced 2025-09-06 06:37:01 +00:00
Code Issues Packages Projects Releases 1 Wiki Activity

fix: solist_drop_so_path explanation comment correctness

Browse Source 
This commit fixes the explanation of why "solist_drop_so_path". ReZygisk does not "dlclose" in ptracer, and doesn't "dlclose" libzygisk.so at any point, but clean SoInfo traces then munmaps it later.
This commit is contained in:
ThePedroo
2025-05-04 18:24:21 -03:00
parent 313822ddcd
commit 16c4d62cd8
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
loader/src/injector/solist.h
View File

@@ -24,9 +24,9 @@ struct pdg {
called solist, a list with the information of opened objects. called solist, a list with the information of opened objects.
Due to special handling in ptracer, however, it won't heave gaps in the Due to special handling in ptracer, however, it won't heave gaps in the
memory of the list since we will close there, not loading a library creating memory of the list since we will remove the info immediatly after loading
this gap. However, the previously loaded library would remain in the solist, libzygisk.so, so that it doesn't create gaps between current module info
requiring ReZygisk to clean those up. and the next (soinfo).
To do that, we use 2 functions: soinfo_free, and set_size, which will To do that, we use 2 functions: soinfo_free, and set_size, which will
zero the region size, and then remove all traces of that library (libzygisk.so) zero the region size, and then remove all traces of that library (libzygisk.so)