Android JNI 报错（signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr ）

已于 2023-07-18 22:18:49 修改
阅读量9.6k 收藏 1
点赞数
CC 4.0 BY-SA版权
分类专栏： 【Other】 文章标签： android android studio ide
于 2021-08-17 16:18:12 首次发布
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-NC-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/SHH_1064994894/article/details/119759492
该日志记录了Android设备上一个由于尝试关闭预期未拥有文件描述符引发的崩溃问题。错误源于fdsan，即文件描述符 sanitizer，它检测到试图关闭的文件描述符342已被另一个唯一标识为0x79499d63b8的文件描述符占用。崩溃发生在与硬件服务交互的过程中，具体在XXXXXXX_DEFAULT服务的XXXXXXX_RECV_DATA函数中。崩溃调用栈涉及到了JNI、Binder进程间通信以及线程管理等。问题可能与不正确的文件描述符管理或并发操作有关。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

 目前看是线程调用问题引起的 ， 错误Log如下：


F DEBUG   : uid: 1000
F DEBUG   : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
F DEBUG   : Abort message: 'fdsan: attempted to close file descriptor 342, expected to be unowned, actually owned by unique_fd 0x79499d63b8'
F DEBUG   :     x0  0000000000000000  x1  00000000000002ac  x2  0000000000000006  x3  0000007825ff7dc0
F DEBUG   :     x4  0000000000000000  x5  0000000000000000  x6  0000000000000000  x7  0000000000000040
F DEBUG   :     x8  00000000000000f0  x9  885261ca2e96c8ec  x10 0000000000000002  x11 0101010101010101
F DEBUG   :     x12 0000000000000038  x13 000000006112a376  x14 0010b0760c06eb20  x15 00004bf984ec6238
F DEBUG   :     x16 0000007b9bb87c80  x17 0000007b9bb692d0  x18 0000007816f7a000  x19 0000000000000100
F DEBUG   :     x20 00000000000002ac  x21 0000007825ff7bb8  x22 0000007826009000  x23 0000000000000003
F DEBUG   :     x24 0000007825ff7eb0  x25 0000007825ff7b30  x26 0000007825ff7af0  x27 ffffff80ffffffc8
F DEBUG   :     x28 00000000130e2480  x29 0000007825ff7e50
F DEBUG   :     lr  0000007b9bb215a0  sp  0000007825ff7a70  pc  0000007b9bb215c4  pst 0000000000001000
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=538.50146, y[0]=146.43742, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=1, eventTime=207254, downTime=207235, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=536.50323, y[0]=144.93806, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=207271, downTime=207235, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=535.50415, y[0]=142.93892, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=207305, downTime=207235, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_UP, actionButton=0, id[0]=0, x[0]=535.50415, y[0]=142.93892, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=207323, downTime=207235, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NavigationBar0]: enqueueInputEvent: event = MotionEvent { action=ACTION_OUTSIDE, actionButton=0, id[0]=0, x[0]=554.4866, y[0]=-2062.0571, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=207397, downTime=207397, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@85f11b8
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_DOWN, actionButton=0, id[0]=0, x[0]=554.4866, y[0]=133.94276, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=207397, downTime=207397, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=551.4894, y[0]=138.94063, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=1, eventTime=207423, downTime=207397, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_POINTER_DOWN(1), actionButton=0, id[0]=0, x[0]=551.4894, y[0]=138.94063, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=1062.0166, y[1]=1642.2981, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=207423, downTime=207397, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=549.1593, y[0]=141.27182, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=1061.0176, y[1]=1642.2981, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=2, historySize=1, eventTime=207441, downTime=207397, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_MOVE, actionButton=0, id[0]=0, x[0]=549.4912, y[0]=142.43913, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=1061.0176, y[1]=1642.2981, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=2, historySize=1, eventTime=207456, downTime=207397, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_POINTER_UP(1), actionButton=0, id[0]=0, x[0]=549.4912, y[0]=141.93935, toolType[0]=TOOL_TYPE_FINGER, id[1]=1, x[1]=1061.0176, y[1]=1642.2981, toolType[1]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=2, historySize=0, eventTime=207471, downTime=207397, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
V ViewRootImpl[NotificationShade]: enqueueInputEvent: event = MotionEvent { action=ACTION_UP, actionButton=0, id[0]=0, x[0]=549.4912, y[0]=141.93935, toolType[0]=TOOL_TYPE_FINGER, buttonState=0, classification=NONE, metaState=0, flags=0x0, edgeFlags=0x0, pointerCount=1, historySize=0, eventTime=207480, downTime=207397, deviceId=4, source=0x1002, displayId=0 },processImmediately = true,mProcessInputEventsScheduled = false, this = android.view.ViewRootImpl@7961aa1
F DEBUG   : backtrace:
F DEBUG   :       #00 pc 00000000000525c4  /apex/com.android.runtime/lib64/bionic/libc.so (fdsan_error(char const*, ...)+584) (BuildId: e1e8eb5e5af955a1237062585bcd4103)
F DEBUG   :       #01 pc 00000000000522c4  /apex/com.android.runtime/lib64/bionic/libc.so (android_fdsan_close_with_tag+728) (BuildId: e1e8eb5e5af955a1237062585bcd4103)
F DEBUG   :       #02 pc 0000000000052a14  /apex/com.android.runtime/lib64/bionic/libc.so (close+16) (BuildId: e1e8eb5e5af955a1237062585bcd4103)
F DEBUG   :       #03 pc 000000000001d588  /system/lib64/hw/XXXXXXX.default.so (XXXXXXX_Recv_Data+220) (BuildId: 8ea9cb858f9e07f9f46e2667695e7f73)
F DEBUG   :       #04 pc 0000000000010fb0  /system/lib64/hw/XXXXXXX.default.so (XXXXXXX_Recv_Total_Data+40) (BuildId: 8ea9cb858f9e07f9f46e2667695e7f73)
F DEBUG   :       #05 pc 000000000001369c  /system/lib64/hw/XXXXXXX.default.so (XXXXXXX_SYMMETRY_ExtKey_Update+252) (BuildId: 8ea9cb858f9e07f9f46e2667695e7f73)
F DEBUG   :       #06 pc 0000000000021548  /system/lib64/hw/XXXXXXX.default.so (XXXXXXX_SYMMETRY_ExtKey_Update+108) (BuildId: 8ea9cb858f9e07f9f46e2667695e7f73)
F DEBUG   :       #07 pc 00000000000a1838  /system/lib64/libandroid_servers.so (android::XXXXXXXUpdateWithExternKey(_JNIEnv*, _jclass*, int, _jbyteArray*, int, _jbyteArray*)+300) (BuildId: 7b24715925318e898834e959142e824b)
F DEBUG   :       #08 pc 00000000005ed0c8  /system/framework/oat/arm64/services.odex (art_jni_trampoline+216) (BuildId: a73b061189f8866f355b3b3fbacd14f0e71e983c)
F DEBUG   :       #09 pc 00000000005f1f34  /system/framework/oat/arm64/services.odex (com.android.server.XXXXXXXService.XXXXXXXUpdateWithExternKey+148) (BuildId: a73b061189f8866f355b3b3fbacd14f0e71e983c)
F DEBUG   :       #10 pc 0000000002047780  /memfd:jit-cache (deleted) (offset 0x2000000) (android.hardware.IXXXXXXXService$Stub.onTransact+5056)
F DEBUG   :       #11 pc 00000000006d30a8  /system/framework/arm64/boot-framework.oat (android.os.Binder.execTransactInternal+712) (BuildId: cb40bb60dea784fc5c91727443635ece3046a254)
F DEBUG   :       #12 pc 00000000006d2cb8  /system/framework/arm64/boot-framework.oat (android.os.Binder.execTransact+296) (BuildId: cb40bb60dea784fc5c91727443635ece3046a254)
F DEBUG   :       #13 pc 0000000000133564  /apex/com.android.art/lib64/libart.so (art_quick_invoke_stub+548) (BuildId: 16e7d67479d4fab1064b63613451746c)
F DEBUG   :       #14 pc 00000000001a8a6c  /apex/com.android.art/lib64/libart.so (art::ArtMethod::Invoke(art::Thread*, unsigned int*, unsigned int, art::JValue*, char const*)+200) (BuildId: 16e7d67479d4fab1064b63613451746c)
F DEBUG   :       #15 pc 000000000054a034  /apex/com.android.art/lib64/libart.so (art::JValue art::InvokeVirtualOrInterfaceWithVarArgs<art::ArtMethod*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, art::ArtMethod*, std::__va_list)+468) (BuildId: 16e7d67479d4fab1064b63613451746c)
F DEBUG   :       #16 pc 000000000054a1d4  /apex/com.android.art/lib64/libart.so (art::JValue art::InvokeVirtualOrInterfaceWithVarArgs<_jmethodID*>(art::ScopedObjectAccessAlreadyRunnable const&, _jobject*, _jmethodID*, std::__va_list)+92) (BuildId: 16e7d67479d4fab1064b63613451746c)
F DEBUG   :       #17 pc 000000000039d98c  /apex/com.android.art/lib64/libart.so (art::JNI<false>::CallBooleanMethodV(_JNIEnv*, _jobject*, _jmethodID*, std::__va_list)+644) (BuildId: 16e7d67479d4fab1064b63613451746c)
F DEBUG   :       #18 pc 000000000009c3bc  /system/lib64/libandroid_runtime.so (_JNIEnv::CallBooleanMethod(_jobject*, _jmethodID*, ...)+124) (BuildId: 37c9f455caf075bbbd023f776c4bfbfe)
F DEBUG   :       #19 pc 000000000012309c  /system/lib64/libandroid_runtime.so (JavaBBinder::onTransact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+156) (BuildId: 37c9f455caf075bbbd023f776c4bfbfe)
F DEBUG   :       #20 pc 000000000004983c  /system/lib64/libbinder.so (android::BBinder::transact(unsigned int, android::Parcel const&, android::Parcel*, unsigned int)+232) (BuildId: a413cfd9d08090f0dd0bc1ee6de89016)
F DEBUG   :       #21 pc 0000000000052254  /system/lib64/libbinder.so (android::IPCThreadState::executeCommand(int)+1056) (BuildId: a413cfd9d08090f0dd0bc1ee6de89016)
F DEBUG   :       #22 pc 0000000000051d84  /system/lib64/libbinder.so (android::IPCThreadState::getAndExecuteCommand()+156) (BuildId: a413cfd9d08090f0dd0bc1ee6de89016)
F DEBUG   :       #23 pc 00000000000525dc  /system/lib64/libbinder.so (android::IPCThreadState::joinThreadPool(bool)+60) (BuildId: a413cfd9d08090f0dd0bc1ee6de89016)
F DEBUG   :       #24 pc 0000000000078970  /system/lib64/libbinder.so (android::PoolThread::threadLoop()+24) (BuildId: a413cfd9d08090f0dd0bc1ee6de89016)
F DEBUG   :       #25 pc 0000000000015414  /system/lib64/libutils.so (android::Thread::_threadLoop(void*)+260) (BuildId: 4868adbd42643f4c59035cf91f86828c)
F DEBUG   :       #26 pc 00000000000a1944  /system/lib64/libandroid_runtime.so (android::AndroidRuntime::javaThreadShell(void*)+140) (BuildId: 37c9f455caf075bbbd023f776c4bfbfe)
F DEBUG   :       #27 pc 0000000000014cd8  /system/lib64/libutils.so (thread_data_t::trampoline(thread_data_t const*)+412) (BuildId: 4868adbd42643f4c59035cf91f86828c)
F DEBUG   :       #28 pc 00000000000af82c  /apex/com.android.runtime/lib64/bionic/libc.so (__pthread_start(void*)+64) (BuildId: e1e8eb5e5af955a1237062585bcd4103)
F DEBUG   :       #29 pc 00000000000500d0  /apex/com.android.runtime/lib64/bionic/libc.so (__start_thread+64) (BuildId: e1e8eb5e5af955a1237062585bcd4103)
D StatusBar: disable1: 0x00000000 -> 0x00000000 (diff1: 0x00000000)
D StatusBar: disable2: 0x00000000 -> 0x00000000 (diff2: 0x00000000)

问题参考:

(11条消息) 文件描述符排错程序 (fdsan)_LlanyW的专栏-CSDN博客

诊断原生代码崩溃问题  |  Android 开源项目  |  Android Open Source Project (google.cn)

android signal 6,android项目运行出现Fatal signal 6 (SIGABRT), code -6 in tid 3
weixin_31140959的博客
05-28 2037
07-2619:45:51.01931718-31866/com.example.administrator.haiweitwoE/art:0xf487b000SpaceTypeMallocSpacebegin=0x12c00000,end=0x12fc4000,limit=0x32c00000,size=3MB,capacity=256MB,non_growth_limit_capa...
android10 crash,Android 10 调用会Crash.
weixin_36423062的博客
05-28 1073
On Sat, 31 Oct 2020 at 13:32, 周枇杷！ ***@***.***> wrote:###Android 10 调用会Crash.-堆栈如下--logversion:utraceaProcess Name: 'com.angel.league'Thread Name: 'RxCachedThreadS'pid: 1030, tid: 2968 >>&gt...
关于android call method fail signal 6 (SIGABRT)_的原因
情随事迁个人博客
12-09 284
出现错误的原因有几种比如调用对象方法却传错对象我经常把class作为对象传递进去 或者是非静态方法我用静态调用之类的。
MySQL：mysqld got signal 6
最新发布
喝醉酒的小白
06-22 693
MySQL InnoDB 存储引擎遇到严重阻塞，导致多个线程在等待信号量（semaphore）超过600秒，最终触发了致命崩溃。这个参数可以从1逐步增加到6（越高恢复越强硬，风险越大）用来导出数据。InnoDB 中的信号量等待时间超过600秒，说明内部资源竞争严重阻塞，导致线程无法继续。从日志中看到写入速度（inserts/s）高达85，且读写量巨大，可能导致锁争用严重。断言失败，表明程序检测到状态不符合预期，可能是内部数据结构不一致。多个线程争抢InnoDB内部锁（信号量），长时间未释放。
Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4693 (GLThread 139), pid 4338
Megumi99的博客
10-16 1467
闪退报错：Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 4693 (GLThread 139), pid 4338。在配置清单文件文件中application中添加 android:allowNativeHeapPointerTagging="false"官方文档中有说明：似乎是targetsdk导致的不兼容问题。而我的targetsdk版本是34。
signal 6 (SIGABRT), code -6 (SI_TKILL) Abort message: ‘stack corruption detected (-fstack-protector
m0_37910557的博客
12-18 4384
在测试调用native的rw_i93.cc文件的rw_i93_sm_format函数时，出现程序crash，报错信息如下 12-18 11:19:39.056 1453 2114 I WifiStateMachine: checkScoreBasedQuality - mPreviousScore[0]:81 mPreviousScore[1]:81 mPreviousScore[2]:81 s2Score:80mPrevoiusScoreAverage:81 12-18 11:19:39.113 ...
关于linux signal 6 (SIGABRT)
热门推荐
张同光 (Tongguang Zhang)：Hello everyone !
11-26 3万+
关于linux signal 6 (SIGABRT)
signal 6 (SIGABRT), code -6 name: RenderThread问题记录
一步一个脚印，可以走的更远。
08-15 1万+
关于signal 6 (SIGABRT), code -6 name: RenderThread异常的调试记录 开发项目中遇到了一个比较难受的异常，报错信息基本上都是指向地址 比如：#452362之类的，看的很头疼，不知如何，排查了很久，终究找到有类似问题的帖子，特此记录解决方案 问题描述： 项目中使用到了USB摄像头，有个场景是使用USB摄像头进行拍照，刚开始测试的次数少，没有发现，后来现场...
解决一个信号6问题(sig6,signal6,SIGABRT,double free or corruption (!prev))
We do not claim to have achieved that goal in every aspect of the software, but we strive for it.
09-04 3万+
我遇到的信号6 99%都是由于数据越界导致，在memcpy的时候没有错误，在free的时候系统报SIGABRT。今天也不例外。代码是我写的，考虑不周，以后拷贝更多加小心。 上图中的data大小为1024，如果memcpy 1025各字节，拷贝正常，但是在你free它的时候就会报上面截图中的错误。这就是原因。遇到这种问题不要怕，新手不要给自己设置障碍，信号是系统提供给你的帮助，而不是困难。...
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr
03-29
好的，用户遇到了关于Android开发中的SIGABRT信号错误，需要找到原因和解决方案。首先，我需要回顾一下相关的知识，并结合提供的引用资料来整理出合理的回答。 首先，SIGABRT（信号6）通常表示程序自身调用了abort...
2025-03-09 01:35:45.642 2212-2212 DEBUG pid-2212 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 01:35:46.219 2240-2240 DEBUG pid-2240 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 01:38:23.760 2908-2908 DEBUG crash_dump64 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 01:38:24.364 2938-2938 DEBUG pid-2938 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr
03-10
首先，用户提供的日志显示有多个进程（pid-2212、2240、2908、2938）在接收到信号6（SIGABRT）后崩溃，错误代码为SI_QUEUE。SIGABRT通常表示程序主动调用了abort()，可能由严重错误导致，比如内存访问问题、资源泄漏...
分析这段bug是什么问题及其解决方法2025-03-09 01:45:29.622 3360-3360 DEBUG pid-3360 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 01:45:54.798 3432-3432 DEBUG pid-3432 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 01:45:55.327 3465-3465 DEBUG pid-3465 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 01:46:21.976 3540-3540 DEBUG pid-3540 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 01:46:39.397 3652-3652 DEBUG pid-3652 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
03-10
pid-3360 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- ``` - `fault addr --------`表示无明确内存地址，说明崩溃点可能在逻辑检查层而非直接的内存访问 - 多进程连续崩溃（pid-3360→pid-3652...
2025-03-09 16:22:37.890 4740-4740 DEBUG crash_dump64 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 16:23:15.450 4831-4831 DEBUG crash_dump64 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr -------- 2025-03-09 16:23:16.109 4862-4862 DEBUG pid-4862 A signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
03-10
每个记录都显示signal 6（SIGABRT），code -1（SI_QUEUE），fault addr是空。这说明程序在运行时主动调用了abort()函数，导致崩溃。需要确定是什么原因触发了abort。 接下来，回顾之前用户的问题，我之前已经给出过...
flutter 插件错误 Fatal signal 6 (SIGABRT), code -6 in tid 10469
qq_32319999的博客
07-04 7482
07-04 10:25:08.397 10469 10469 F flutter : [FATAL:flutter/shell/platform/android/platform_view_android_jni.cc(61)] Check failed: CheckException(env). 07-04 10:25:08.398 10469 10469 F libc    : Fatal s...
android fault addr,signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr
weixin_29172201的博客
05-27 6331
摘抄自：http://zhidao.baidu.com/link?url=gOXPCxE4HSq9GOGH0QGNS5zLXUWkeeHrmWpD_W3DrUllNLgJF7OGV4RCAEQGDGQlQv6J_8b-7zXNBDtUnAzUr1vw5UCBmC16i8oMhgkrO8eJave层的代码发生crash问题时，系统往往会打印出很详细的出错信息。比如上面这个例子，不但给出了出错的原因，...
环信集成报错Fatal signal 6 (SIGABRT), code -6 in tid 28957 (Thread-2)
Yaobinbin_的博客
04-14 956
这个错误应该是极少出现的，是我自己粗心导致报错 Fatal signal 6 (SIGABRT), code -6 in tid 28957 (Thread-2) 这是因为在环信集成的时候要配置Appkey
android signal 6,android signal 处理总结
weixin_28882149的博客
05-28 1642
在Android 开发中遇到一些signal 的情况，简要总结如下：1)Zygote 监控 子进程的退出情况jellybean/dalvik/vm/native/dalvik_system_Zygote.cpp#151151 sa.sa_handler = sigchldHandler;153 err = sigaction (SIGCHLD, &sa, NULL);当进程...
JNI 出现fatal signal 6 (SIGABRT) at ...
dianqun1977的博客
09-02 2042
因为将JNI方法写在了另一个类里面，所以不能在JNI的类中调用MainActivity中的方法，将JNI类中的native方法放在MainActivity中就没问题。 问题：如何在JNI类中的方法中回调非JNI类中的方法执行java代码呢？ 因为这些方法是对象方法，他们的执行需要一个对象，所以在native执行中，我们通过反射的时候在哪里获取了那个方法的对象呢？ 直接调用了那个ca...
Android 显示Gif 动态图片
2401_84009317的博客
03-30 618
网上学习 Android的资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。网上学习 Android的资料一大堆，但如果学到的知识不成体系，遇到问题时只是浅尝辄止，不再深入研究，那么很难做到真正的技术提升。帮助大家学习提升进阶，也节省大家在网上搜索资料的时间来学习，也可以分享给身边好友一起学习。家学习提升进阶，也节省大家在网上搜索资料的时间来学习，也可以分享给身边好友一起学习。// 从描述文件中读出gif的值，创建出Movie实例。
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

一歲抬頭

点赞1元，收藏免费，打赏随意。

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付：¥1
获取中
扫码支付

您的余额不足，请更换扫码支付或充值

打赏作者

实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值