HarmonyOS 鸿蒙Next Reason:Signal:SIGSEGV(SEGV_MAPERR)定位不到具体位置

发布于 1周前 作者 caililin 最后一次编辑是 5天前 来自 鸿蒙OS

HarmonyOS 鸿蒙Next Reason:Signal:SIGSEGV(SEGV_MAPERR)定位不到具体位置

Module name:com.xxx.xxxx.hos
Version:1.0.0

VersionCode:99999999

PreInstalled:No

Foreground:No

Timestamp:2024-07-20 13:29:30.519

Pid:24134

Uid:20020034

Process name:com.xxx.xxxx.hos

Process life time:26s

Reason:Signal:SIGSEGV(SEGV_MAPERR)@000000000000000000  probably caused by NULL pointer dereference

Fault thread info:

Tid:24174, Name:OS_TaskWorker

#00 pc 00000000004bb9c5 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#01 pc 000000000046b46b /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#02 pc 00000000004b9a73 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#03 pc 000000000048a683 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#04 pc 000000000048a26d /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#05 pc 000000000049e7eb /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#06 pc 00000000004a40c7 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#07 pc 00000000004ac922 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#08 pc 0000000000335778 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#09 pc 000000000055bc31 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#10 pc 000000000055bb89 /system/lib64/platformsdk/libark_jsruntime.so(panda::ecmascript::ObjectFactory::NewJSObject(panda::ecmascript::JSHandle<panda::ecmascript::JSHClass> const&)+25)(15f41da5673f6be9fe08ea3d48bd4dcb)

#11 pc 000000000043ac29 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#12 pc 0000000000415f58 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#13 pc 0000000000415d1a /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#14 pc 00000000003eff57 /system/lib64/module/arkcompiler/stub.an(RTStub_AsmInterpreterEntry+151)

Registers:

  rax:00007f092336e310 rdx:0000000000000000 rcx:00007f0919593a70 rbx:00007f0919593a50

  rsi:0000000000000000 rdi:00007f092336deb0 rbp:ffff000000000006 rsp:00007f0918e49bb8

  r8:0000000000000000 r9:00007f092febbb30 r10:0000000000000002 r11:00007f092febbb50

  r12:00007f0918e49d20 r13:00007f0918e49bf8 r14:0000000000000000 r15:00007f0918e49bf4 rip:00007f092febb9c5

Other thread info:

Tid:24134, Name:azq.xxx.hos

#00 pc 00000000001194c9 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#01 pc 000000000011e0d7 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#02 pc 0000000000135ca8 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#03 pc 000000000008c1fc /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

Tid:24136, Name:IPC_0_24136

#00 pc 00000000000d4feb /system/lib/ld-musl-x86_64.so.1(ioctl+187)(e72bad3cd463f78e2206bc50d72eb535)

#01 pc 000000000000e04d /system/lib64/chipset-pub-sdk/libipc_common.z.so(OHOS::BinderConnector::WriteBinder(unsigned long, void*)+61)(b973e18489efbdd8d1bff5e06e6e09de)

#02 pc 00000000000528c1 /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::TransactWithDriver(bool)+289)(ff82313a9167d426a7391bbc15831c29)

#03 pc 0000000000052a3c /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::StartWorkLoop()+60)(ff82313a9167d426a7391bbc15831c29)

#04 pc 00000000000540b7 /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::JoinThread(bool)+39)(ff82313a9167d426a7391bbc15831c29)

#05 pc 000000000004d46e /system/lib64/platformsdk/libipc_core.z.so(OHOS::IPCWorkThread::ThreadHandler(void*)+494)(ff82313a9167d426a7391bbc15831c29)

#06 pc 000000000011cc47 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#07 pc 000000000008c2d2 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

Tid:24137, Name:IPC_1_24137

#00 pc 00000000000d4feb /system/lib/ld-musl-x86_64.so.1(ioctl+187)(e72bad3cd463f78e2206bc50d72eb535)

#01 pc 000000000000e04d /system/lib64/chipset-pub-sdk/libipc_common.z.so(OHOS::BinderConnector::WriteBinder(unsigned long, void*)+61)(b973e18489efbdd8d1bff5e06e6e09de)

#02 pc 00000000000528c1 /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::TransactWithDriver(bool)+289)(ff82313a9167d426a7391bbc15831c29)

#03 pc 0000000000052a3c /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::StartWorkLoop()+60)(ff82313a9167d426a7391bbc15831c29)

#04 pc 00000000000540b7 /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::JoinThread(bool)+39)(ff82313a9167d426a7391bbc15831c29)

#05 pc 000000000004d41a /system/lib64/platformsdk/libipc_core.z.so(OHOS::IPCWorkThread::ThreadHandler(void*)+410)(ff82313a9167d426a7391bbc15831c29)

#06 pc 000000000011cc47 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#07 pc 000000000008c2d2 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

Tid:24148, Name:IPC_2_24148

#00 pc 00000000000d4feb /system/lib/ld-musl-x86_64.so.1(ioctl+187)(e72bad3cd463f78e2206bc50d72eb535)

#01 pc 000000000000e04d /system/lib64/chipset-pub-sdk/libipc_common.z.so(OHOS::BinderConnector::WriteBinder(unsigned long, void*)+61)(b973e18489efbdd8d1bff5e06e6e09de)

#02 pc 00000000000528c1 /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::TransactWithDriver(bool)+289)(ff82313a9167d426a7391bbc15831c29)

#03 pc 0000000000052a3c /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::StartWorkLoop()+60)(ff82313a9167d426a7391bbc15831c29)

#04 pc 00000000000540b7 /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::JoinThread(bool)+39)(ff82313a9167d426a7391bbc15831c29)

#05 pc 000000000004d41a /system/lib64/platformsdk/libipc_core.z.so(OHOS::IPCWorkThread::ThreadHandler(void*)+410)(ff82313a9167d426a7391bbc15831c29)

#06 pc 000000000011cc47 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#07 pc 000000000008c2d2 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

Tid:24149, Name:OS_GC_Thread

#00 pc 00000000004bcf57 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#01 pc 00000000004bcf05 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#02 pc 0000000000320bcd /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#03 pc 00000000004b5d24 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#04 pc 00000000004ba1fe /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#05 pc 00000000004a5ed8 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#06 pc 00000000005d60b5 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#07 pc 00000000005d68c9 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#08 pc 000000000011cc47 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#09 pc 000000000008c2d2 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

Tid:24150, Name:OS_GC_Thread

#00 pc 00000000001194c9 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#01 pc 000000000011ad63 /system/lib/ld-musl-x86_64.so.1(pthread_cond_timedwait+163)(e72bad3cd463f78e2206bc50d72eb535)

#02 pc 00000000005d6b4e /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#03 pc 00000000005d6085 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#04 pc 00000000005d68c9 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#05 pc 000000000011cc47 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#06 pc 000000000008c2d2 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

Tid:24151, Name:OS_GC_Thread

#00 pc 00000000001193c0 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#01 pc 00000000000bc78f /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#02 pc 00000000000b5439 /system/lib64/libc++.so(operator new(unsigned long)+25)(c0ed1ecd94ec3912926aceba672056047399739b)

#03 pc 00000000004ba1b7 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#04 pc 00000000004a5ed8 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#05 pc 00000000005d60b5 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#06 pc 00000000005d68c9 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#07 pc 000000000011cc47 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#08 pc 000000000008c2d2 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

Tid:24152, Name:OS_GC_Thread

#00 pc 00000000001194c9 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#01 pc 000000000011ad63 /system/lib/ld-musl-x86_64.so.1(pthread_cond_timedwait+163)(e72bad3cd463f78e2206bc50d72eb535)

#02 pc 00000000005e4b1a /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#03 pc 00000000005e474e /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#04 pc 00000000005e4db6 /system/lib64/platformsdk/libark_jsruntime.so(15f41da5673f6be9fe08ea3d48bd4dcb)

#05 pc 000000000011cc47 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

#06 pc 000000000008c2d2 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)

Tid:24154, Name:OS_FFRT_Delay

#00 pc 00000000000d6a6c /system/lib/ld-musl-x86_64.so.1(syscall+348)(e72bad3cd463f78e2206bc50d72eb535)

#01 pc 000000000006c1d1 /system/lib64/chipset-sdk/libffrt.so(743a3eb3f6fdb0641f0118652c3a2d52)

#02 pc 000000000011cc47 /system/lib/ld-musl-x86_64.so.1(e72bad3cd463f78e2206bc50d72eb535)
5 回复

楼主您好，该问题需要demo分析，建议通过在线提单提交问题。

支持 - 在线提单 - 华为开发者联盟 (huawei.com)

感谢！该问题已解决

楼主，你好打扰了，请教您一下，我也遇到了类似问题，希望了解一下您是怎么解决的

楼主，你好打扰了，请教您一下，我也遇到了类似问题,希望了解一下你那边的排查方式

在HarmonyOS开发中遇到SIGSEGV（SEGV_MAPERR）错误，这通常指示尝试访问无效的内存地址。由于这是一个运行时错误，且信号SIGSEGV是硬件异常，定位可能较为困难。建议检查以下几点：

  1. 审查最近的代码改动，特别是与指针操作和内存分配相关的部分。
  2. 使用调试工具（如GDB）运行程序，查看崩溃时的堆栈跟踪，以获取更多上下文。
  3. 检查是否有数组越界、野指针或未初始化的指针使用。
  4. 验证所有动态分配的内存是否已正确释放，避免内存泄漏或双重释放。

如果问题依旧没法解决请加我微信，我的微信是itying888。

回到顶部