Class
GumModuleRegistry
Description [src]
final class Gum.ModuleRegistry : GObject.Object
{
/* No available fields */
}Low-level registry of the process’s loaded modules, emitting signals as libraries are loaded and unloaded.
Most code should reach for the higher-level Process API, such as
gum_process_enumerate_modules(), or a GumModuleMap snapshot. Use
the registry directly when you need to know when modules come and go:
obtain it with Gum.ModuleRegistry.obtain and connect to its
GumModuleRegistry::module-added and
GumModuleRegistry::module-removed signals. Hold
gum_module_registry_lock() across a sequence of operations that need a
stable view.
Functions
gum_module_registry_set_rtld_notifier_offsets
Overrides the dynamic-linker notifier hook location(s) used when the registry is activated. Instead of hooking the well-known notifier stub, Frida hooks the given call sites, each computed as the dynamic linker base plus an offset.
Instance methods
gum_module_registry_lock
Acquires the registry lock, preventing concurrent modification while held.
Use this to keep the module set stable across several operations, for example
while holding on to a GumModule obtained from it. Balance with
gum_module_registry_unlock(). Enumeration already takes the lock internally.
Signals
Signals inherited from GObject (1)
GObject::notify
The notify signal is emitted on an object when one of its properties has its value set through g_object_set_property(), g_object_set(), et al.