Debug sentry-kotlin-multiplatform issue 341 and sentry-cocoa

[buenaflor]

📜 Description

Adds a detailed analysis document (issue-341-analysis.md) for issue #341, which describes the problem of incorrect stack traces being captured on iOS when using captureException.

💡 Motivation and Context

This document provides a deep dive into the root cause of why captureException on iOS captures the current thread's stack trace instead of the original NSException's stack trace. It analyzes both the Sentry Kotlin Multiplatform and Sentry Cocoa SDKs, identifies the specific points of failure, and proposes a clear solution to ensure proper stack trace capture for Kotlin/Native exceptions on iOS.

💚 How did you test it?

This PR introduces a documentation/analysis file. The analysis itself serves as the verification of the problem and the proposed solution, based on code examination and understanding of both SDKs. No new code tests were added as this is not a code change.

📝 Checklist

You have to check all boxes before merging:

• I reviewed the submitted code.
• I added tests to verify the changes. (N/A - documentation)
• No new PII added or SDK only sends newly added PII if sendDefaultPII is enabled. (N/A - documentation)
• I updated the docs if needed. (This PR is the documentation)
• Review from the native team if needed. (Potentially, as it discusses Sentry Cocoa SDK behavior)
• No breaking change or entry added to the changelog. (N/A - documentation)

🔮 Next steps

The next step is to implement the proposed fix within the Sentry Cocoa SDK to ensure NSException.callStackReturnAddresses are correctly utilized when capturing exceptions on iOS.

---

_{Learn more about Cursor Agents}

[github-actions]

	Fails
🚫	Please consider adding a changelog entry for the next release.

Instructions and example for changelog

Please add an entry to CHANGELOG.md to the "Unreleased" section. Make sure the entry includes this PR's number.

Example:

## Unreleased

- Debug sentry-kotlin-multiplatform issue 341 and sentry-cocoa ([#440](https://github.com/getsentry/sentry-kotlin-multiplatform/pull/440))

If none of the above apply, you can opt out of this check by adding #skip-changelog to the PR description.

Generated by 🚫 dangerJS against 8fa1083