![]() I/DEBUG ( 31): #06 pc 0000d362 /system/lib/libc.soĪndroid NDK includes a command ndk-stack that can help match the addresses with actual source files of your code, which is based on the addr2line utility in NDK toolchain. It works well if I run the following command. ![]() Please find the configuration file below. I/DEBUG ( 31): #03 pc 000191ac /system/lib/libc.so I am using Crashlytic sdk for collecting Android NDK crash reports. Bugly Tencent Bugly scm::BuglyDevTeam/Bugly-Android-NDK.git. you can enable full stack traces and detailed crash reports for your native. It also seems to happen more on some devices than others. Get Android NDK crash reports Firebase Crashlytics - Google firebase Crashlytics libc.so - Stack Overflow Multiple various libc.so crashes in production. I/DEBUG ( 31): r0 0000af88 r1 0000a008 r2 baadf00d r3 0d9f00d8 The bug involves garbage collection and background processes, so it can seem sort of random. I/DEBUG ( 31): signal 11 (SIGSEGV), fault addr 0d9f00d8 I/DEBUG ( 31): pid: 351, tid: 351 > /data/local/ndk-tests/crasher <<< Hi there, was wondering if anyone here has managed to get crash reporting working for Android apps using the NDK. There is a good chance that you will see a stack trace, like I/DEBUG ( 31): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** To learn how to report NDK crashes, refer to the Android SDK documentation for Android apps, or Unity SDK documentation for Unity apps. Instead of the Run tab, look at the Logcat. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |