kscrashsentry_installCPPExceptionHandler issues @kstenerud about kscrash

[alexmedearis]

I am also seeing a similar stack trace in KSCrash. I can see the full exception stack track in Crashlytics, but only a crash in the CLSTerminateHandler on the KSCrash side.

I am kind of confused by the interaction of crashlytics and kscrash when handling an exception. It looks from the stack trace(s) as though KSCrash is successfully running its crash handler, then passing control to Crashlytics, which is crashing.

KSCrash runs first, and at the bottom of CPPExceptionTerminate (KSCrashSentry_CPPException.mm) it calls g_originalTerminateHandler which goes into the Crashlytics one which triggers a SIGABRT. I'm wondering if that might be the expected behavior of Crashlytics, which KSCrash mistakenly treats as a crash instead of handling the exception or if there is something more complex going on.

It is worth noting that the crashlytics docs say to start crashlytics last, which I believe means that it should actually be executing its handlers first:
http://support.crashlytics.com/knowledgebase/articles/92506-are-you-compatible-with-other-sdks

I'm going to try experimenting with ordering to see if the problem goes away.