From 16c4d62cd83eb37e442cb37fc3d91091fcef4ca7 Mon Sep 17 00:00:00 2001 From: ThePedroo Date: Sun, 4 May 2025 18:24:21 -0300 Subject: [PATCH] fix: `solist_drop_so_path` explanation comment correctness 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. --- loader/src/injector/solist.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/loader/src/injector/solist.h b/loader/src/injector/solist.h index db726c1..5c33e73 100644 --- a/loader/src/injector/solist.h +++ b/loader/src/injector/solist.h @@ -24,9 +24,9 @@ struct pdg { called solist, a list with the information of opened objects. 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 - this gap. However, the previously loaded library would remain in the solist, - requiring ReZygisk to clean those up. + memory of the list since we will remove the info immediatly after loading + libzygisk.so, so that it doesn't create gaps between current module info + and the next (soinfo). 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)