EXC_BAD_ACCESS自动处理(EXC_BAD_ACCESS automatic handli

2019-06-23 23:12发布

我试图建立自己的信号,并为iOS未捕获的异常处理程序。 要做到这一点,我使用这两个函数:

NSSetUncaughtExceptionHandler(/*handler*/); 

signal(/*signal const*/, /*signal handler*/);

我的问题是,我不能使它与EXC_BAD_ACCESS信号的工作。 有一些信号不变(如SIGABRT,SIGBUS)搭上EXC_BAD_ACCESS? 如果没有,我该如何处理呢? 有些崩溃分析工具(利卡PLCrashReporter,Crashlytics等)可以跟踪它...

Answer 1:

EXC_BAD_ACCESS这样你第一个功能不与工作的情况下不会产生的异常。 它产生一个信号SIGSEGVSIGBUS

请参阅处理未处理的异常和信号由可可与爱。

更新

我只是检查LLDB的源代码。 这可能是TARGET_EXC_BAD_ACCESS = 0x91。

在RNBRemote.h:

/* We translate the /usr/include/mach/exception_types.h exception types
   (e.g. EXC_BAD_ACCESS) to the fake BSD signal numbers that gdb uses
   in include/gdb/signals.h (e.g. TARGET_EXC_BAD_ACCESS).  These hard
   coded values for TARGET_EXC_BAD_ACCESS et al must match the gdb
   values in its include/gdb/signals.h.  */

#define TARGET_EXC_BAD_ACCESS      0x91
#define TARGET_EXC_BAD_INSTRUCTION 0x92
#define TARGET_EXC_ARITHMETIC      0x93
#define TARGET_EXC_EMULATION       0x94
#define TARGET_EXC_SOFTWARE        0x95
#define TARGET_EXC_BREAKPOINT      0x96

在RNBRemote.cpp:

// Translate any mach exceptions to gdb versions, unless they are
// common exceptions like a breakpoint or a soft signal.
switch (tid_stop_info.details.exception.type)
{
    default:                    signum = 0; break;
    case EXC_BREAKPOINT:        signum = SIGTRAP; break;
    case EXC_BAD_ACCESS:        signum = TARGET_EXC_BAD_ACCESS; break;
    case EXC_BAD_INSTRUCTION:   signum = TARGET_EXC_BAD_INSTRUCTION; break;
    case EXC_ARITHMETIC:        signum = TARGET_EXC_ARITHMETIC; break;
    case EXC_EMULATION:         signum = TARGET_EXC_EMULATION; break;
    case EXC_SOFTWARE:
        if (tid_stop_info.details.exception.data_count == 2 &&
            tid_stop_info.details.exception.data[0] == EXC_SOFT_SIGNAL)
            signum = tid_stop_info.details.exception.data[1];
        else
            signum = TARGET_EXC_SOFTWARE;
        break;
}


文章来源: EXC_BAD_ACCESS automatic handling