如何从 libc.so、libart.so 修复 Android Native Crash

分类：编程问答

如何解决如何从 libc.so、libart.so 修复 Android Native Crash

我们的应用程序不包含任何 c/c++ 代码，而我们使用一些包含 .so 的第三方 sdk

现在，我们发现了很大一部分本地崩溃？

我们找不到有用的信息来获得哪个sdk承担责任。 并且崩溃指向 ，例如“libc.so”、“libart.so”和“/system/framework/arm/boot-framework.oat”

那么，我该怎么做才能解决崩溃问题？ 升级sdk？但我不知道升级哪个

我无法获得我们应用的任何信息...

============================================

Process Name: 'com.xxxxxxxxxxx'
Thread Name: 'RenderThread'
pid: 23247,tid: 13872  >>> com.xxxx <<<
signal 6 (SIGABRT),code -1 (SI_QUEUE),fault addr --------
    r0 00000000  r1 00003630  r2 00000006  r3 b71adb30
    r4 b71adb44  r5 b71adb28  r6 00005acf  r7 0000016b
    r8 b71adb40  r9 b71adb30  10 b71adb60  fp b71adb50
    ip 00003630  sp b71adb00  lr e6ed9deb  pc e6ed9dfe  cpsr 
    008f0030
    d0  696c657069504c47  d1  6e65704f61696b53
    d2  7577682f7362696c  d3  696c657069702f69
    d4  0000000000000000  d5  0000000000000000
    d6  0000000000000000  d7  0000000000000000
    d8  0000000000000000  d9  0000000000000000
    d10 0000000000000000  d11 0000000000000000
    d12 0000000000000000  d13 0000000000000000
    d14 0000000000000000  d15 0000000000000000
    d16 ffffffffffffffff  d17 2e6761742e676f6c
    d18 e6eb8769e6eb8761  d19 e6eb8775e6eb8771
    d20 0000000000000000  d21 0000000000000000
    d22 0000000000fffdd6  d23 0000000000ffff5a
    d24 0000000000ffffeb  d25 0000000001000000
    d26 0000000000000000  d27 000000000000001d
    d28 0000000000000000  d29 000000001d000000
    d30 00d600d600d600d6  d31 0000000000000000
    scr 28000093

    #00  pc 0002ddfe  /apex/com.android.runtime/lib/bionic/libc.so (abort)
    #00  pc 0002ddfe  /apex/com.android.runtime/lib/bionic/libc.so
    #01  pc 0002ddeb  /apex/com.android.runtime/lib/bionic/libc.so
    --- --- ---
[DEBUG] Read self maps instead! map: 0x0
    00 pc 0002ddfe  /apex/com.android.runtime/lib/bionic/libc.so 
  (abort+165)
    01 pc 00001aad  liblog.so (__android_log_assert+176)
    02 pc 00124ff7  libhwui.so
    03 pc 00122bdd  libhwui.so
    04 pc 00122131  libhwui.so
    05 pc 001308b9  libhwui.so
    06 pc 0013070b  libhwui.so
    07 pc 000039af  libutils.so 
    (_ZN7android6Thread11_threadLoopEPv+210)
    08 pc 0007a22d  /apex/com.android.runtime/lib/bionic/libc.so 
    (_ZL15__pthread_startPv+20)
    09 pc 0002f2a9  /apex/com.android.runtime/lib/bionic/libc.so 
   (__start_thread+30)
--- --- ---
    --- --- --- ---

memory near r1:
    00003630 -------- -------- -------- --------  ................

memory near r3:
    b71adaf0 e662537d b71adb28 00005acf 0000007e  }Sb.(....Z..~...
    b71adb00 b71adb70 b71adb80 b71adb90 b71adba0  p...............
    b71adb10 a6363000 8e60f3d2 00021d02 a8b02323  .06...`.....##..
    b71adb20 0000000f 00000003 ffffffdf ffffffff  ................
    b71adb30 00000000 00000000 ffffffff 00005acf  .............Z..
    b71adb40 00002735 00000000 00000000 00000000  5'..............
    b71adb50 00000000 00000000 00000000 00000000  ................
    b71adb60 00000000 00000000 00000000 00000000  ................
    b71adb70 00000000 00000000 00000000 00000000  ................
    b71adb80 00000000 00000000 00000000 00000000  ................
    b71adb90 00000000 00000000 00000000 00000000  ................
    b71adba0 00000000 00000000 00000000 00000000  ................
    b71adbb0 00000000 00000000 00000000 00000000  ................
    b71adbc0 b71adbf8 e662537d e918f0b2 d722ad50  ....}Sb.....P.".
    b71adbd0 0000007e b71ae060 ffffffff b71ae060  ~...`.......`...
    b71adbe0 9434e1bc e9191ab1 e6608a45 b71ae00c  ..4.....E.`.....

解决方法

修复来自外部 SDK 的本机崩溃总是很困难。一种尝试是检查发生崩溃时获得的整个堆栈跟踪。顶部可能只有十六进制地址，但更深的地方可能有一些代码行，这实际上可能对您有所帮助。例如，请参阅我们的应用程序中发生的崩溃：

 *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0,tid: 0 >>> one.realnote.app <<<

backtrace:
  #00  pc 0000000000fc40d4  /data/app/com.google.ar.core-SbkhfyZZQu51a6XNR_3aGQ==/base.apk!libarcore_c.so (offset 0x6e0000)
  #00  pc 0000000000fc358c  /data/app/com.google.ar.core-SbkhfyZZQu51a6XNR_3aGQ==/base.apk!libarcore_c.so (offset 0x6e0000)
  #00  pc 0000000000fc29ec  /data/app/com.google.ar.core-SbkhfyZZQu51a6XNR_3aGQ==/base.apk!libarcore_c.so (offset 0x6e0000)
  #00  pc 0000000000fc2478  /data/app/com.google.ar.core-SbkhfyZZQu51a6XNR_3aGQ==/base.apk!libarcore_c.so (offset 0x6e0000)
  #00  pc 0000000001951958  /data/app/com.google.ar.core-SbkhfyZZQu51a6XNR_3aGQ==/base.apk!libarcore_c.so (offset 0x6e0000)
  #00  pc 000000000193eb2c  /data/app/com.google.ar.core-SbkhfyZZQu51a6XNR_3aGQ==/base.apk!libarcore_c.so (offset 0x6e0000) (ArSession_update+152)
  #00  pc 000000000000eb8c  /data/app/one.realnote.app-g6hR_qK9swLsb5Br8mzp-Q==/base.apk!lib/arm64-v8a/libarcore_sdk_jni.so (offset 0x6a1000) (Java_com_google_ar_core_Session_nativeUpdate+48)
  #00  pc 0000000000076cfc  /data/app/one.realnote.app-g6hR_qK9swLsb5Br8mzp-Q==/oat/arm64/base.odex (art_jni_trampoline+140)
  #00  pc 00000000020c90c0  /memfd:/jit-cache (com.google.ar.sceneform.ArSceneView.onBeginFrame+368)
  #00  pc 00000000020d1274  /memfd:/jit-cache (com.google.ar.sceneform.SceneView.doFrameNoRepost+164)
  #00  pc 00000000020c259c  /memfd:/jit-cache (com.google.ar.sceneform.SceneView.doFrame+172)
  #00  pc 0000000000a2bed4  /system/framework/arm64/boot-framework.oat (android.view.Choreographer.doCallbacks+692)
  #00  pc 0000000000a2c668  /system/framework/arm64/boot-framework.oat (android.view.Choreographer.doFrame+1224)
  #00  pc 0000000000b07038  /system/framework/arm64/boot-framework.oat (android.view.Choreographer$FrameDisplayEventReceiver.run+72)
  #00  pc 00000000007eeadc  /system/framework/arm64/boot-framework.oat (android.os.Handler.dispatchMessage+76)
  #00  pc 00000000007f21b8  /system/framework/arm64/boot-framework.oat (android.os.Looper.loop+1448)
  #00  pc 0000000000552294  /system/framework/arm64/boot-framework.oat (android.app.ActivityThread.main+772)
  #00  pc 00000000001375b8  /apex/com.android.runtime/lib64/libart.so (art_quick_invoke_static_stub+568)
  #00  pc 00000000001460cc  /apex/com.android.runtime/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*,unsigned int*,unsigned int,art::JValue*,char const*)+276)
  #00  pc 00000000004b24b8  /apex/com.android.runtime/lib64/libart.so (art::(anonymous namespace)::InvokeWithArgArray(art::ScopedObjectAccessAlreadyRunnable const&,art::ArtMethod*,art::(anonymous namespace)::ArgArray*,char const*)+104)
  #00  pc 00000000004b3f00  /apex/com.android.runtime/lib64/libart.so (art::InvokeMethod(art::ScopedObjectAccessAlreadyRunnable const&,_jobject*,unsigned long)+1472)
  #00  pc 000000000043f658  /apex/com.android.runtime/lib64/libart.so (art::Method_invoke(_JNIEnv*,_jobjectArray*)+48)
  #00  pc 00000000000c8c34  /system/framework/arm64/boot.oat (art_jni_trampoline+180)
  #00  pc 0000000000aaa8f8  /system/framework/arm64/boot-framework.oat (com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run+136)
  #00  pc 0000000000ab3044  /system/framework/arm64/boot-framework.oat (com.android.internal.os.ZygoteInit.main+3012)
  #00  pc 00000000001375b8  /apex/com.android.runtime/lib64/libart.so (art_quick_invoke_static_stub+568)
  #00  pc 00000000001460cc  /apex/com.android.runtime/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*,char const*)+104)
  #00  pc 00000000004b2118  /apex/com.android.runtime/lib64/libart.so (art::InvokeWithVarArgs(art::ScopedObjectAccessAlreadyRunnable const&,_jmethodID*,std::__va_list)+408)
  #00  pc 00000000003bc968  /apex/com.android.runtime/lib64/libart.so (art::JNI::CallStaticVoidMethodV(_JNIEnv*,_jclass*,std::__va_list)+624)
  #00  pc 00000000000eeafc  /system/lib64/libandroid_runtime.so (_JNIEnv::CallStaticVoidMethod(_jclass*,...)+116)
  #00  pc 00000000000f1c1c  /system/lib64/libandroid_runtime.so (android::AndroidRuntime::start(char const*,android::Vector<android::String8> const&,bool)+804)
  #00  pc 00000000000034f0  /system/bin/app_process64 (main+1184)
  #00  pc 000000000007e86c  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108)

一些十六进制计数器，但在内部的某个地方，您可以看到类似 com.google.ar.sceneform.SceneView.doFrameNoRepost+164 的调用，它为您提供崩溃的 SDK（我们的 ARCore）以及崩溃的区域。通过这种方式，您可以检入您的代码，在那里您有与该特定 SDK 行为的联系点，并检查您这边可能存在的错误。如果您还没有这样做，我建议您使用具有本机支持的 ​​Firebase Crashlytics 在在线控制台中获取堆栈跟踪。

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容， 请发送邮件至 dio@foxmail.com 举报，一经查实，本站将立刻删除。

相关推荐

导入项目后报错问题
依赖报错 idea导入项目后依赖报错，解决方案：https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错：更换其他版本 无法下载依赖可参考：https://blog.csdn.net/weixin_42628809/a
idea不能识别yaml文件
使用mybatis plus常见错误
错误1：代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
gradle常见问题与错误
错误1：gradle项目控制台输出为乱码 # 解决方案：https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
Mybatis Plus传入参数0不起作用
错误还原：在查询的过程中，传入的workType为0时，该条件不起作用 &lt;select id=&quot;xxx&quot;&gt; SELECT di.id, di.name, di.work_type, di.updated... &lt;where&gt; &lt;if test=&qu
linux中make编译源码包失败
报错如下，gcc版本太低 ^ server.c:5346:31: 错误：‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
微服务启动错误：Command line is too long. Shorten command line for
解决方案1 1、改项目中.idea/workspace.xml配置文件，增加dynamic.classpath参数 2、搜索PropertiesComponent，添加如下 &lt;property name=&quot;dynamic.classpath&quot; value=&quot;tru
vue常见错误
删除根组件app.vue中的默认代码后报错：Module Error (from ./node_modules/eslint-loader/index.js): 解决方案：关闭ESlint代码检测，在项目根目录创建vue.config.js，在文件中添加 module.exports = { lin
spark常见错误
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
matplotlib报错：AttributeError: module 'backend_interagg' has no attribute 'FigureCanvas'. Did you mean: 'FigureCanvasAgg'?
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams[&#39;font.sans-serif&#39;] = [&#39;SimHei&#39;] # 能正确显示负号 p
gitlab登录失败，报错：This challenge page was accidentally cached by an intermediary and is no longer available.
设置时间 控制面板
后端开发常见错误
错误1：Request method ‘DELETE‘ not supported 错误还原：controller层有一个接口，访问该接口时报错：Request method ‘DELETE‘ not supported 错误原因：没有接收到前端传入的参数，修改为如下 参考 错误2：cannot r
docker常见错误
错误1：启动docker镜像时报错：Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法：重启docker -&gt; systemctl r
idea常见错误
错误1：private field ‘xxx‘ is never assigned 按Altʾnter快捷键，选择第2项 参考：https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2：启动时报错，不能找到主启动类 #
pip安装依赖失败
报错如下，通过源不能下载，最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
maven常见错误
错误1：maven打包报错 错误还原：使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
cloud项目中常见错误
错误1：服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping(&quot;/hires&quot;) public class FeignControl
springboot常见错误
错误1：运行项目后报如下错误 解决方案 报错2：Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案：在pom.
springmvc拦截器中使用redisTemplate报空指针异常
参考 错误原因 过滤器或拦截器在生效时，redisTemplate还没有注入 解决方案：在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate&lt;String
vite报错：npm ERR! command C:WINDOWSsystem32cmd.exe /d /s /c C:UsersychenAppDataLocalTempnpx-dde1c848.cmd
使用vite构建项目报错 C:\Users\ychen\work&gt;npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-
pythonJavaScriptjavaHTMLPHPreactjsC#AndroidCSSNode.jssqlrpython-3.xMysqLjQueryc++pandasFlutterangularIOSdjangolinuxswifttypescript路由器JSON路由器设置无线路由器h3c华三华三路由器设置华三路由器电脑软件教程arraysdocker软件图文教程Cvue.jslaravelspring-boot