android11墓碑机制和addr2line使用

最新推荐文章于 2025-01-10 18:24:40 发布

原创

最新推荐文章于 2025-01-10 18:24:40 发布 · 6.1k 阅读

3 ·

CC 4.0 BY-SA版权

文章标签：

#arm #linux

本文记录了在Android 11系统上遇到的墓碑异常，详细展示了错误日志，特别是涉及到surfaceflinger进程的问题。通过addr2line工具定位到libc.so库中的初始化函数出错，但未明确给出解决方案。分析提到可能是硬件问题，静电导致短路。同时介绍了addr2line的使用方法，用于从.so文件中查找函数调用栈。

文章目录

一、问题所在
二、addr2line使用
- 一、找到对应的工具目录

开发板为rockchip的3566,版本android11。

一、问题所在

这两天调试开发板出现了一个问题。就是这个安卓的墓碑机制，他会有一些类似的报错，就是一大段DEBUG的错误

[   12.289543] DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
[   12.290103] DEBUG: Build fingerprint: 'xxxxxxxxx/1.0/eng.xxxxxxx.20211125.143115:userdebug/release-keys'
[   12.290499] DEBUG: Revision: '0'
[   12.290741] DEBUG: ABI: 'arm64'
[   12.291302] DEBUG: Timestamp: 1970-01-01 00:00:12+0000
[   12.291721] DEBUG: pid: 148, tid: 148, name: surfaceflinger  >>> /system/bin/surfaceflinger <<<
[   12.291917] DEBUG: uid: 1000
[   12.292256] DEBUG: signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
[   12.292599] DEBUG: Abort message: 'eglQueryStringImplementationANDROID(EGL_VERSION) failed'
[   12.292855] DEBUG:     x0  0000000000000000  x1  0000000000000094  x2  0000000000000006  x3  0000007fc97017f0
[   12.293088] DEBUG:     x4  0000000029aaaaf1  x5  0000000029aaaaf1  x6  0000000029aaaaf1  x7  00000073e6cb3000
[   12.293460] DEBUG:     x8  00000000000000f0  x9  00000073e46bf6d8  x10 ffffff80ffffffdf  x11 0000000000000001
[   12.293726] DEBUG:     x12 0000007fc97017b0  x13 0000000000000038  x14 ff00000000000000  x15 ffffffffffffffff
[   12.293986] DEBUG:     x16 00000073e478f948  x17 00000073e476ea60  x18 00000073e6692000  x19 0000000000000094
[   12.294233] DEBUG:     x20 0000000000000094  x21 00000000ffffffff  x22 0000000300000001  x23 0000000000000001
[   12.294479] DEBUG:     x24 0000000000000003  x25 0000000000000000  x26 0000000000000000  x27 0000000000000000
[   12.294735] DEBUG:     x28 0000000000000000  x29 0000007fc9701870
[   12.295071] DEBUG:     lr  00000073e4722888  sp  0000007fc97017d0  pc  00000073e47228b8  pst 0000000000001000
[   12.353908] DEBUG: 
[   12.354009] DEBUG: backtrace:
[   12.354354] DEBUG:       #00 pc 00000000000898b8  /apex/com.android.runtime/lib64/bionic/libc.so (abort+168) (BuildId: d33c7ee9ce128fbcab34ed8529cd06f3)
[   12.354875] DEBUG:       #01 pc 00000000000062e4  /system/lib64/liblog.so (__android_log_default_aborter+12) (BuildId: 796c64bd8c172c74bbe9d13be7fdb14b)
[   12.355207] DEBUG:       #02 pc 0000000000006e58  /system/lib64/liblog.so (__android_log_assert+336) (BuildId: 796c64bd8c172c74bbe9d13be7fdb14b)
[   12.355684] DEBUG:       #03 pc 000000000018a498  /system/lib64/libsurfaceflinger.so (android::renderengine::gl::GLESRenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+4496) (BuildId: 2e50c52a66754342019ef33b8c2aa865)
[   12.356158] DEBUG:       #04 pc 000000000018914c  /system/lib64/libsurfaceflinger.so (android::renderengine::RenderEngine::create(android::renderengine::RenderEngineCreationArgs const&)+168) (BuildId: 2e50c52a66754342019ef33b8c2aa865)
[   12.356639] DEBUG:       #05 pc 0000000000109a68  /system/lib64/libsurfaceflinger.so (android::SurfaceFlinger::init()+184) (BuildId: 2e50c52a66754342019ef33b8c2aa865)
[   12.357011] DEBUG:       #06 pc 00000000000021b8  /system/bin/surfaceflinger (main+368) (BuildId: a89eb6c00bbdc77278f0b6b1fee2e129)
[   12.357349] DEBUG:       #07 pc 0000000000084e58  /apex/com.android.runtime/lib64/bionic/libc.so (__libc_init+108) (BuildId: d33c7ee9ce128fbcab34ed8529cd06f3)
hierarchy support. Nested cgroups may change behavior in the future.
[    8.762858] cgroup: "memory" requires setting use_hierarchy to 1 on the root
[    8.969083] ueventd: ueventd started!
[    8.977701] selinux: SELinux: Loaded file_contexts
[    8.977786] selinux: 
[    8.978516] ueventd: Parsing file /system/etc/ueventd.rc...
[    8.980727] ueventd: Parsing file /vendor/ueventd.rc...
[    8.983512] ueventd: /vendor/ueventd.rc: 60: invalid gid 'net_bt_stack'
[    8.983744] ueventd: /vendor/ueventd.rc: 61: invalid gid 'net_bt_stack'
[    8.983952] ueventd: /vendor/ueventd.rc: 62: invalid gid 'net_bt_stack'
[    8.984157] ueventd: /vendor/ueventd.rc: 64: invalid gid 'net_bt_stack'
[    8.984726] ueventd: /vendor/ueventd.rc: 118: invalid gid 'trace'
[    9.020004] apexd: This device does not support updatable APEX. Exiting
[    9.532057] bifrost_kbase: disagrees about version of symbol module_layout
[    9.597749] rknpu: disagrees about version of symbol module_layout
[    9.655403] rknpu: disagrees about version of symbol module_layout
[   10.580265] Registered swp emulation handler
[   10.711775] EXT4-fs (mmcblk0p10): Ignoring removed nomblk_io_submit option
[   10.779042] EXT4-fs (mmcblk0p10): mounted filesystem with ordered data mode. Opts: errors=remount-ro,nomblk_io_submit
[   10.802954] logd.auditd: start
[   10.803129] logd.klogd: 10658326406
[   10.862832] e2fsck: e2fsck 1