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

Parse native threads from AppExitInfo for native crashes #3295

Open
romtsn opened this issue Apr 2, 2024 · 3 comments
Open

Parse native threads from AppExitInfo for native crashes #3295

romtsn opened this issue Apr 2, 2024 · 3 comments

Comments

@romtsn
Copy link
Member

romtsn commented Apr 2, 2024

Description

We can enrich native crashes even further by parsing traceInputStream when the reason was REASON_CRASH_NATIVE

Bugsnag prior art https://github.com/bugsnag/bugsnag-android/tree/next/bugsnag-plugin-android-exitinfo/src/main/java/com/bugsnag/android

@supervacuus
Copy link

FYI: This is related with the investigation here: getsentry/sentry-native#743 (comment)

@supervacuus
Copy link

However, tombstones won't necessarily decode what caused the SIGABRT. There is a good chance that the SIGABRT was an unhandled C++ exception, which would require a terminate handler to decode what happened.

@markushi
Copy link
Member

markushi commented Apr 3, 2024

Let's still enrich the native envelopes with matching AppExitInfo, as we already have all the necessary parts ready.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Status: Backlog
Development

No branches or pull requests

3 participants