HarmonyOS鸿蒙Next中崩溃报错的crash信息无法定位具体错误

HarmonyOS鸿蒙Next中崩溃报错的crash信息无法定位具体错误 Device info: OpenHarmony 3.2
Build info: OpenHarmony 3.2.9.1
Module name: com.lxy.wanharmony
Version: 1.0.0
Pid: 7997
Uid: 20040021
Reason: Signal: SIGFPE(FPE_INTDIV)
Thread name: com.lxy.wanharm

#00 pc 00000000015ebfd8 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#01 pc 00000000015ec200 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#02 pc 00000000015ec4dd /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#03 pc 00000000015ecbe0 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#04 pc 00000000013eed0e /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#05 pc 0000000001475402 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#06 pc 0000000001476ad4 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#07 pc 00000000013eed0e /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#08 pc 000000000158ab7f /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#09 pc 00000000013eed0e /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#10 pc 00000000013ea001 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#11 pc 00000000013eed0e /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#12 pc 00000000015ecccf /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#13 pc 00000000013eed0e /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#14 pc 00000000016162d2 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#15 pc 00000000013eed0e /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#16 pc 00000000013a04d4 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#17 pc 0000000000e893a3 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#18 pc 0000000000e89619 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#19 pc 0000000000e7c546 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#20 pc 0000000000e3b948 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#21 pc 0000000000e3c867 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#22 pc 0000000000daa78f /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#23 pc 0000000000daa746 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#24 pc 0000000000ece291 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#25 pc 0000000000ece193 /system/lib64/libace.z.so (482e7a90e9ff2e241a79a9c405a9730c)
#26 pc 0000000000056a2e /system/lib64/libwm.z.so(OHOS::Rosen::VsyncStation::VsyncCallbackInner(long)+462) (f95fb786ec09f797f608460d011a73cc)
#27 pc 0000000000056ae3 /system/lib64/libwm.z.so(OHOS::Rosen::VsyncStation::OnVsync(long, void*)+19) (f95fb786ec09f797f608460d011a73cc)
#28 pc 000000000001be58 /system/lib64/libvsync.z.so(OHOS::Rosen::VsyncCallBackListenerContainer::OnReadable(int)+552) (7a122da5ede1093d8fc0e2655c379afe)
#29 pc 0000000000017ed7 /system/lib64/platformsdk/libeventhandler.z.so (6dd02bcdad70c6551a80ce5f415f6603)
#30 pc 0000000000010ca9 /system/lib64/platformsdk/libeventhandler.z.so(OHOS::AppExecFwk::EventHandler::DistributeEvent(std::__h::unique_ptr<OHOS::AppExecFwk::InnerEvent, void ()(OHOS::AppExecFwk::InnerEvent)> const&)+505) (6dd02bcdad70c6551a80ce5f415f6603)
#31 pc 000000000001ad52 /system/lib64/platformsdk/libeventhandler.z.so (6dd02bcdad70c6551a80ce5f415f6603)
#32 pc 00000000000196a8 /system/lib64/platformsdk/libeventhandler.z.so(OHOS::AppExecFwk::EventRunner::Run()+56) (6dd02bcdad70c6551a80ce5f415f6603)
#33 pc 0000000000087ce0 /system/lib64/libappkit_native.z.so(OHOS::AppExecFwk::MainThread::Start()+480) (94ca62b6337e500de1050d413f61e30c)
#34 pc 000000000001572c /system/bin/appspawn (2778b21557cf967b8bf23975a093a84f)
#35 pc 0000000000015825 /system/bin/appspawn (2778b21557cf967b8bf23975a093a84f)
#36 pc 0000000000014f7c /system/bin/appspawn (2778b21557cf967b8bf23975a093a84f)
#37 pc 000000000002c44a /system/lib64/libbegetutil.z.so (aa9b33d17515ab6026831e5e0aeb274f)
#38 pc 000000000002c173 /system/lib64/libbegetutil.z.so (aa9b33d17515ab6026831e5e0aeb274f)
#39 pc 0000000000029f85 /system/lib64/libbegetutil.z.so(ProcessEvent+85) (aa9b33d17515ab6026831e5e0aeb274f)
#40 pc 0000000000029af1 /system/lib64/libbegetutil.z.so (aa9b33d17515ab6026831e5e0aeb274f)
#41 pc 00000000000141e6 /system/bin/appspawn (2778b21557cf967b8bf23975a093a84f)
#42 pc 00000000000125ca /system/bin/appspawn (2778b21557cf967b8bf23975a093a84f)
#43 pc 0000000000090cf9 /vendor/aosp/system/lib64/libc.so(__libc_init+89) (2de37b8aa6e96dd64a6cfa51bd78ae6e)

这样的错误堆栈信息属实看不太懂呀！


更多关于HarmonyOS鸿蒙Next中崩溃报错的crash信息无法定位具体错误的实战教程也可以访问 https://www.itying.com/category-93-b0.html

6 回复

SIGFPE 浮点异常 进程执行了错误的算术运算，如除数为0、浮点溢出、整数溢出等。

看起来是一个除以零的错误（FPE_INTDIV）。这种错误通常是由程序中的除法操作中出现了0导致的。要解决这个问题，您需要检查代码中的除法操作，确保分母不为0。另外，您可以尝试更新操作系统和相关的库文件，以确保使用的是最新版本。

更多关于HarmonyOS鸿蒙Next中崩溃报错的crash信息无法定位具体错误的实战系列教程也可以访问 https://www.itying.com/category-93-b0.html


感谢回答，鸿蒙开发目前的崩溃日志确实定位不是很好，我这个问题是swiper组件没有初始值时出现的问题。

我也是，乖乖，

找HarmonyOS工作还需要会Flutter的哦，有需要Flutter教程的可以学学大地老师的教程，很不错，B站免费学的哦：BV1S4411E7LY/?p=17

我也是在使用Swiper组件中出现的崩溃，但是没找到什么地方没有什么初始值，

在HarmonyOS鸿蒙Next中，若崩溃报错的crash信息无法定位具体错误，建议采取以下步骤：

  • 首先，确保开发环境配置正确，包括SDK和IDE版本。
  • 其次，使用日志工具如HiLog进行详细日志记录，帮助追踪问题源头。
  • 然后，检查代码中的异常处理机制，确保所有可能的异常都被捕获和处理。
  • 最后，利用调试工具逐步执行代码，观察变量和程序状态，以发现潜在的错误。

如果问题依旧，建议查阅官方文档或社区论坛，寻求更专业的帮助。

回到顶部