Philip Niedertscheider
Philip Niedertscheider
@kode54 the NSException crash monitor should already use the `callStackReturnAddresses` here: https://github.com/getsentry/sentry-cocoa/blob/fbb76563c954bab9c13baa2b70a1f0962230c97f/Sources/SentryCrash/Recording/Monitors/SentryCrashMonitor_NSException.m#L69-L73 There's also #741 where @philipphofmann recently [brought up](https://github.com/getsentry/sentry-cocoa/issues/741#issuecomment-2754406219) that the callStackReturnAddresses could be used for it.
I digged into the code again and while the crash monitor uses the callStackReturnAddresses, the SentryStacktraceBuilder does not - sorry for the confusion on my side. To collect some insights...
Closing this due to inactivity. If this is still relevant for you, feel free to comment and provide current information, or open an new issue
cc @stefanosiano
I will close this issue, as we will not do this for at least another year. At least we have it documented now and issues search should bring it up...
Hi @brunojdo, as far as I am aware there has not been any progress so far. @buenaflor can you please confirm this?
@philipphofmann are you going to pick this up?
@cursor review @sentry review
After reconsideration and learnings while working on #6957 I decided that I will move this feature to be marked as "experimental" first to keep some leeway to react if the...
What's the status of this PR? I see it is outdated and has merge conflicts due to being open for a while now.