Closed atsushieno closed 3 years ago
It seems current libglib-2.0.so from cerbero output seems invalid, as it results in loading failure at lilv_lib_open() (which is dlopen()):
lilv_lib_open()
dlopen()
2021-05-24 02:33:35.460 5742-5742/org.androidaudioplugin.aap_fluidsynth E/lilv: lilv_lib_open(): Failed to open library /lv2/aap-fluidsynth.lv2/libaap-fluidsynth.so (dlopen failed: cannot locate symbol "__lttf2" referenced by "/data/app/~~SNgvVfr4MXPangBO32-P1w==/org.androidaudioplugin.aap_fluidsynth-kpQ7C6fRcPO6mUMqq7wn5g==/base.apk!/lib/x86_64/libglib-2.0.so"...) 2021-05-24 02:33:35.460 5742-5742/org.androidaudioplugin.aap_fluidsynth E/lilv: lilv_plugin_instantiate(): failed to open library: file:///lv2/aap-fluidsynth.lv2/libaap-fluidsynth.so in /lv2/aap-fluidsynth.lv2/ 2021-05-24 02:33:38.458 5742-5742/org.androidaudioplugin.aap_fluidsynth A/libc: Fatal signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 in tid 5742 (.aap_fluidsynth), pid 5742 (.aap_fluidsynth)
arm64 has been causing loading failure for some different message but would fall into the same kind of issue.
Closing this as it does not seem to be an issue in libglib-2.0.so as per https://github.com/atsushieno/aap-lv2-fluidsynth/issues/1#issuecomment-846816967.
It seems current libglib-2.0.so from cerbero output seems invalid, as it results in loading failure at
lilv_lib_open()
(which isdlopen()
):arm64 has been causing loading failure for some different message but would fall into the same kind of issue.