This might be controversial but to parse module info for UI, we'd need to use sceKernelLoadStartModule to retrieve exported symbol information but it would also run module_start due to how we defined it in the crtprx in the SDK.
With the exception of the loader. We don't ship these in release builds and to run the loader module_start is required at least without changes from GoldHEN internal loader.
This will break compatibility with built in loader in GoldHEN 2.3.
This might be controversial but to parse module info for UI, we'd need to use
sceKernelLoadStartModule
to retrieve exported symbol information but it would also runmodule_start
due to how we defined it in the crtprx in the SDK.With the exception of the loader. We don't ship these in release builds and to run the loader
module_start
is required at least without changes from GoldHEN internal loader.This will break compatibility with built in loader in GoldHEN 2.3.