sentry-cocoa: `SentryCrashMonitor` crashes on macOS and iOS

Environment

How do you use Sentry?

Sentry SaaS (sentry.io)

Which SDK and version?

7.5.2

Steps to Reproduce

  1. Look at this report: https://sentry.io/organizations/sindresorhus/issues/2847452452/events/76b39b939f954ff1b446cf770b33d3ba/
  2. Notice how it crashed in “Sources/SentryCrash/Recording/Monitors/SentryCrashMonitor_CPPException.cpp:169”

Expected Result

I expected the crash monitor to not crash.

Actual Result

The reason I think the crash monitor itself is crashing is that the crash reason is EXC_BAD_INSTRUCTION: callStackSymbols. I don’t access callStackSymbols anywhere in my own code.

About this issue

  • Original URL
  • State: closed
  • Created 3 years ago
  • Comments: 21 (8 by maintainers)

Commits related to this issue

Most upvoted comments

Hello, we have also encountered this bug, which is the most frequent bug in our app.

image

OS Version: iOS 15.6.1 (19G82) Report Version: 104

Exception Type: EXC_CRASH (SIGABRT) Crashed Thread: 9

Application Specific Information: NSException > terminating with %s exception of type %s > terminating with uncaught exception of type NSException

Thread 9 Crashed: 0 libsystem_kernel.dylib 0x372199b38 __pthread_kill 1 libsystem_pthread.dylib 0x3e4fd73bc pthread_kill 2 libsystem_c.dylib 0x318e5e524 abort 3 libc++abi.dylib 0x3348bfb7c <redacted> 4 libc++abi.dylib 0x3348af9c4 <redacted> 5 libobjc.A.dylib 0x3346aac68 <redacted> 6 myapp 0x2068abec4 CPPExceptionTerminate (SentryCrashMonitor_CPPException.cpp:171) 7 libc++abi.dylib 0x3348bef18 <redacted> 8 libc++abi.dylib 0x3348beeb4 std::terminate 9 libdispatch.dylib 0x302525a44 <redacted> 10 libdispatch.dylib 0x302528c1c <redacted> 11 libdispatch.dylib 0x302537164 <redacted> 12 libdispatch.dylib 0x30253796c <redacted> 13 libsystem_pthread.dylib 0x3e4fd1080 _pthread_wqthread