原标题不符合修改要求，未提供可修改的标题内容，因此保持原样输出： Reason:Signal:SIGSEGV(SI_KERNEL)@000000000000000000

原标题不符合修改要求，未提供可修改的标题内容，因此保持原样输出：

Reason:Signal:SIGSEGV(SI_KERNEL)@000000000000000000

请教大佬们，运行软件后会出现闪退的情况，并且给出以下报错信息，请教大神给指个解决方式，谢谢

Device info: emulator  
Build info: emulator 5.0.0.112(SP2DEVC00E112R4P11log)  
Fingerprint: 895198b79008699fda60af191bd64e05bcc5cfcac2c2117d7b9f5104721e09a6  
Module name: com.DefaultCompany.TestProject  
Version: 1.0  
VersionCode: 1  
PreInstalled: No  
Foreground: Yes  
Timestamp: 2024-12-13 15:30:13.891  
Pid: 21362  
Uid: 20020044  
Process name: com.DefaultCompany.TestProject  
Process life time: 58s  
Reason: Signal: SIGSEGV(SI_KERNEL)[@000000000000000000](/user/000000000000000000)  

Fault thread info:  
Tid: 21767, Name: TuanjieMain  

#00 pc 00000000000b7f3f /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  
#01 pc 00000000000b7ceb /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  
#02 pc 0000000000d3cc0c /data/storage/el1/bundle/libs/x86_64/libtuanjie.so(59e872a54f8547ad)  
#03 pc 0000000000d48fd6 /data/storage/el1/bundle/libs/x86_64/libtuanjie.so(59e872a54f8547ad)  
#04 pc 0000000000d46943 /data/storage/el1/bundle/libs/x86_64/libtuanjie.so(59e872a54f8547ad)  
#05 pc 0000000000d461e3 /data/storage/el1/bundle/libs/x86_64/libtuanjie.so(59e872a54f8547ad)  
#06 pc 0000000000d4f20b /data/storage/el1/bundle/libs/x86_64/libtuanjie.so(59e872a54f8547ad)  
#07 pc 0000000000017810 /system/lib64/platformsdk/libuv.so(58d2841b6cc10a12203b91a9451acc14)  
#08 pc 0000000000029093 /system/lib64/platformsdk/libuv.so(58d2841b6cc10a12203b91a9451acc14)  
#09 pc 0000000000017dd5 /system/lib64/platformsdk/libuv.so(uv_run+517)(58d2841b6cc10a12203b91a9451acc14)  
#10 pc 0000000000019881 /system/lib64/module/libworker.z.so(8a640feccc947f5ba8a4a82840ace904)  
#11 pc 000000000002cd62 /system/lib64/module/libworker.z.so(8a640feccc947f5ba8a4a82840ace904)  
#12 pc 000000000011ae67 /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  
#13 pc 00000000000893ae /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  

Registers:  
rax: 3a5ebbcfb8470ce7 rdx: 0000000000000000 rcx: 000000000000001f rbx: 00007f482d639c40  
rsi: 00007f483f18b93e rdi: 00007f483f18b910 rbp: 00007f482d639bd0 rsp: 00007f482d639bd0  
r8: 0000000000000000 r9: 00007f482dc5b9c8 r10: 0000000000000010 r11: 0000000000000206  
r12: 00007f483f18b920 r13: 00007f47f0003930 r14: 00007f483f18b920 r15: 00007f483f18b920 rip: 00007f4849eb9f3f  

Other thread info:  
Tid: 21362, Name: any.TestProject  
#00 pc 0000000000117649 /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  
#01 pc 000000000011c347 /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  
#02 pc 000000000012f9f8 /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  
#03 pc 00000000000892d8 /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  

Tid: 21747, Name: OS_IPC_0_21747  
#00 pc 00000000000d15eb /system/lib/ld-musl-x86_64.so.1(ioctl+187)(fb7824806b595afc3892b76169e5e74b)  
#01 pc 0000000000007af5 /system/lib64/chipset-pub-sdk/libipc_common.z.so(OHOS::BinderConnector::WriteBinder(unsigned long, void*)+53)(03ff6d819e22751adba09cd3d442ab10)  
#02 pc 00000000000608ec /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::TransactWithDriver(bool)+284)(b09f87e9eab7660f245629cf125f197c)  
#03 pc 0000000000060c0a /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::StartWorkLoop()+90)(b09f87e9eab7660f245629cf125f197c)  
#04 pc 00000000000628d7 /system/lib64/platformsdk/libipc_core.z.so(OHOS::BinderInvoker::JoinThread(bool)+39)(b09f87e9eab7660f245629cf125f197c)  
#05 pc 0000000000059c55 /system/lib64/platformsdk/libipc_core.z.so(OHOS::IPCWorkThread::ThreadHandler(void*)+805)(b09f87e9eab7660f245629cf125f197c)  
#06 pc 000000000011ae67 /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  
#07 pc 00000000000893ae /system/lib/ld-musl-x86_64.so.1(fb7824806b595afc3892b76169e5e74b)  

Tid: 21748, Name: OS_IPC_1_21748  
... (similar entries for other threads) ...

2 回复

这个问题比较复杂，这个日志信息无法获取到有用的信息，能提供个复现的demo，基于demo继续分析


针对您提供的帖子标题中的错误提示“Reason: Signal: SIGSEGV(SI_KERNEL)@000000000000000000”，这是一个关于鸿蒙系统（HarmonyOS）中可能遇到的段错误（Segmentation Fault）问题。在鸿蒙系统中，SIGSEGV信号表示无效的内存引用，即试图访问未分配或不允许访问的内存地址。

该错误通常发生在以下几种情况：

  1. 空指针解引用：尝试对一个未初始化（或已设为NULL）的指针进行解引用。
  2. 数组越界：访问数组时超出了其分配的内存范围。
  3. 野指针：指针指向了一个随机的内存地址。
  4. 内存释放后使用：访问了已经释放的内存。

解决这类问题通常需要：

  • 检查指针使用：确保所有指针在使用前已正确初始化，且在访问前未被释放或设置为NULL。
  • 数组边界检查：在访问数组元素时，确保索引在有效范围内。
  • 使用工具：利用鸿蒙系统提供的调试工具，如gdb等，进行内存访问跟踪和错误定位。

如果问题依旧没法解决请联系官网客服，官网地址是 https://www.itying.com/category-93-b0.html

回到顶部