You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
The text was updated successfully, but these errors were encountered:
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 includesentry
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.functionpthread_getcpuclockid
(for 2604)/apex/com.android.art/lib64/libart.so
with stack.functionart::Trace::StopTracing
(for 3561)/apex/com.android.art/lib64/libart.so
with stack.functionart::Thread::DumpState
(for 3653)The text was updated successfully, but these errors were encountered: