Sentry catches wrong stacktrace of NSException

[ShiBody]

Platform

macOS

Environment

Production

Installed

Manually

Version

8.40.0

Xcode Version

16.1

Did it work on previous versions?

No response

Steps to Reproduce

1. Raise a NSGenericException with customized fail reason
2. Debug in Xcode could see stacktrace in Exception Backtrace clearly. We have 58 elements in NSExcaption.

3. While after sending to Sentry, we could only see an invalid stacktrace
   https://webex.sentry.io/issues/6504297906/events/6a3940bbdb38430b8a84f9177eb2d854/?project=4507095483809792

Expected Result

Same stacktrace as Exception Backtrace shows

Actual Result

An invalid runloop stacktrace captured.

Are you willing to submit a PR?

No response

[philprime]

Hi @ShiBody, thanks for opening up this issue.

Looking at the crash report in Sentry, have you tried to upload debug symbols to see if it helps with symbolicating the full stack trace? While I agree that the amount of frames seems off, testing the crash with debug symbols might help with pinpointing the issue.

[ShiBody]

Hi @ShiBody, thanks for opening up this issue.

Looking at the crash report in Sentry, have you tried to upload debug symbols to see if it helps with symbolicating the full stack trace? While I agree that the amount of frames seems off, testing the crash with debug symbols might help with pinpointing the issue.

Upload symbol files and got same result:
https://webex.sentry.io/issues/6504297906/events/aba4cc8bf49c41ab97b444f4dedea653/?project=4507095483809792

And sorry guys, this should be a Mac project. I have switched it to MacOS in my project settings, and all my tests are about a Mac App.

[philprime]

Thank you for getting back to us, we'll have to investigate this.