库突然无法在动态链接器(NDK)中加载

发布于 2024-11-29 10:44:18 字数 1618 浏览 0 评论 0原文

我开发 NDK 应用程序已经有一段时间了,并且运行良好。然而,今天,在我进行一些名义上的更改后编译它后,该应用程序随机决定不再启动。这是由加载应用程序主库时出现的神秘问题引起的。以下是一些日志输出:

08-11 18:38:11.220 D/dalvikvm( 1237): Added shared lib /mnt/asec/com.audia.rta-1/lib/libqtandroid.so 0x40513bd8
08-11 18:38:11.220 D/dalvikvm( 1237): No JNI_OnLoad found in /mnt/asec/com.audia.rta-1/lib/libqtandroid.so 0x40513bd8, skipping init
08-11 18:38:11.220 D/dalvikvm( 1237): Trying to load lib /mnt/asec/com.audia.rta-1/lib/librta.so 0x40513bd8
08-11 18:38:11.260 D/AndroidRuntime( 1237): Shutting down VM
08-11 18:38:11.260 W/dalvikvm( 1237): threadid=1: thread exiting with uncaught exception (group=0x40015560)
08-11 18:38:11.260 E/AndroidRuntime( 1237): FATAL EXCEPTION: main
08-11 18:38:11.260 E/AndroidRuntime( 1237): java.lang.UnsatisfiedLinkError: Cannot load library: reloc_library[1311]:    67 cannot locate '_ZNSaIcEC1Ev'...
08-11 18:38:11.260 E/AndroidRuntime( 1237): 
08-11 18:38:11.260 E/AndroidRuntime( 1237):     at java.lang.Runtime.loadLibrary(Runtime.java:434)
08-11 18:38:11.260 E/AndroidRuntime( 1237):     at java.lang.System.loadLibrary(System.java:554)
08-11 18:38:11.260 E/AndroidRuntime( 1237):     at com.audia.rta.RTA.onCreate(RTA.java:139)

根据一些 Google 结果,_ZNSaIcEC1Evlibstdc++ 的一部分。我已经检查过,它在构建过程中被链接,并且 g++ 用于链接。

奇怪的是,恢复到应用程序的较旧 apk 可以解决问题,但编译旧版本并安装并不能解决问题。我的构建系统中的所有内容都已检查到版本控制中,并且我已经完成了几次干净的构建。我今天所有的构建都在工作,然后它们就停止工作了。我没有升级或安装任何东西;它发生在我正在测试新代码的过程中。发生了什么?

更新:从新签出的副本构建并不能解决问题。

更新2:有什么方法可以追踪到该符号的链接,也许可以使用objdump?也许这可以提供一些线索。

I've been developing an NDK app for quite some time and it's been working well. However, today the app randomly decided to not start anymore, after I compiled it after making some nominal change. It's caused by a cryptic problem with loading the app's main library. Here's some log output:

08-11 18:38:11.220 D/dalvikvm( 1237): Added shared lib /mnt/asec/com.audia.rta-1/lib/libqtandroid.so 0x40513bd8
08-11 18:38:11.220 D/dalvikvm( 1237): No JNI_OnLoad found in /mnt/asec/com.audia.rta-1/lib/libqtandroid.so 0x40513bd8, skipping init
08-11 18:38:11.220 D/dalvikvm( 1237): Trying to load lib /mnt/asec/com.audia.rta-1/lib/librta.so 0x40513bd8
08-11 18:38:11.260 D/AndroidRuntime( 1237): Shutting down VM
08-11 18:38:11.260 W/dalvikvm( 1237): threadid=1: thread exiting with uncaught exception (group=0x40015560)
08-11 18:38:11.260 E/AndroidRuntime( 1237): FATAL EXCEPTION: main
08-11 18:38:11.260 E/AndroidRuntime( 1237): java.lang.UnsatisfiedLinkError: Cannot load library: reloc_library[1311]:    67 cannot locate '_ZNSaIcEC1Ev'...
08-11 18:38:11.260 E/AndroidRuntime( 1237): 
08-11 18:38:11.260 E/AndroidRuntime( 1237):     at java.lang.Runtime.loadLibrary(Runtime.java:434)
08-11 18:38:11.260 E/AndroidRuntime( 1237):     at java.lang.System.loadLibrary(System.java:554)
08-11 18:38:11.260 E/AndroidRuntime( 1237):     at com.audia.rta.RTA.onCreate(RTA.java:139)

According to some Google results, _ZNSaIcEC1Ev is part of libstdc++. I've checked, and it gets linked in the build process, and g++ is being used for linking.

Oddly enough, reverting to an older apk of the app fixes the problem, but compiling an old revision and installing that doesn't fix the problem. Everything in my build system is checked into version control, and I've done several clean builds. All my builds were working today and then they just stopped working. I didn't upgrade or install anything; it happened while I was in the middle of testing new code. What happened?

Update: Building from a freshly checked out copy doesn't fix the problem.

Update 2: Is there any way I can track down the link to that symbol, maybe with objdump? Maybe this could provide some clues.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(1

素罗衫 2024-12-06 10:44:18

我最终使用全新的 NDK 安装编译了所有内容,并且它有效。就好像旧的不知何故被损坏了,尽管我不知道是怎么损坏的。

这也是从r5br6的升级,所以可能和NDK版本有关。

I ended up compiling everything with a fresh NDK install, and it worked. It's as if the old one was corrupted somehow, though I have no idea how.

It was also an upgrade from r5b to r6, so maybe it's related to the NDK version.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文