Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDK Crash Detection: Capture SDK-related crashes with specific signatures #81172

Open
kahest opened this issue Nov 22, 2024 · 0 comments
Open
Assignees

Comments

@kahest
Copy link
Member

kahest commented Nov 22, 2024

Sometimes we want to get insights into crashes that are not caused by the SDK directly and where sentry doesn't show up in any stack frame. It'd be useful for these cases to also capture/forward crashes based on specific signatures, even if they don’t include sentry in the stack trace.

At the moment, I suggest capturing the following signatures (all related to Android Runtime tracer crashes):

  • /apex/com.android.art/lib64/bionic/libc.so with stack.function pthread_getcpuclockid (for 2604)
  • /apex/com.android.art/lib64/libart.so with stack.function art::Trace::StopTracing (for 3561)
  • /apex/com.android.art/lib64/libart.so with stack.function art::Thread::DumpState (for 3653)
@philipphofmann philipphofmann self-assigned this Nov 22, 2024
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

No branches or pull requests

2 participants