Skip to content

Conversation

@maxep
Copy link
Member

@maxep maxep commented Nov 4, 2025

What and why?

Add KSCrashBacktrace implementation for capturing thread backtraces using KSCrash's native APIs.

How?

The implementation uses KSCrash's low-level backtrace APIs (ksbt_captureBacktrace and ksbt_symbolicateAddress) to capture and symbolicate stack frames for any thread.

Review checklist

  • Feature or bugfix MUST have appropriate tests (unit, integration)
  • Make sure each commit and the PR mention the Issue number or JIRA reference
  • Add CHANGELOG entry for user facing changes
  • Add Objective-C interface for public APIs (see our guidelines (internal) and run make api-surface)

@maxep maxep force-pushed the maxep/RUM-12420/kscrash-backtrace branch from 9d75c43 to a6d5190 Compare November 4, 2025 17:01
Base automatically changed from maxep/RUM-12420/kscrash-dependency to feature/kscrash November 7, 2025 07:36
@maxep maxep force-pushed the maxep/RUM-12420/kscrash-backtrace branch from a6d5190 to e4b2b85 Compare November 7, 2025 14:48
@maxep maxep marked this pull request as ready for review November 7, 2025 14:48
@maxep maxep requested review from a team as code owners November 7, 2025 14:48
@maxep maxep force-pushed the maxep/RUM-12420/kscrash-backtrace branch 2 times, most recently from 0f6f50c to 112d2cb Compare November 18, 2025 17:06
@maxep maxep force-pushed the maxep/RUM-12420/kscrash-backtrace branch from 112d2cb to 46b19e5 Compare November 19, 2025 08:35
}

// Capture backtrace for the thread
var count: Int32 = 200
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

question/ Why 200 ? Could you maybe add a comment explaining why?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants