topic Re: Android Mobile Crash report | signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) question in Real User Monitoring

Android Mobile Crash report | signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) question

slawek_michalik — Mon, 09 Dec 2024 14:58:58 GMT

Hi *

Prospect asked if crash report collected by mobile agent can point the Dev on SIGSEGV issues.

Can anybody confirm if following statement is correct, please?

In case of Android the situation is clear.

As long as

libnative.so, libc.so

where the issue occurs, are not a part of Android Runtime, there won't be any reference to it in Mobile Crash Report. Please correct me if I'm wrong.

How the issue

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

would work in case of iOS App crashes?

And the last but not least -

Regardless the platform, is it a way to collect mode extensive crash/debug info, so Devs are aware about such problem?

Your suggestions are more than welcome.

Best regards,

Slawek

Re: Android Mobile Crash report | signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) question

Patrick_H — Wed, 09 Oct 2019 07:04:44 GMT

For iOS the signal info is part of the crash report. Please elaborate on the last question, I don't know what it is about (Dynatrace collects crash information and it can be symbolicated to get a human readable stacktrace).

For Android Dynatrace only reports java exception stacktraces and no signals. Dynatrace does not capture native crashes on Android e.g. if NDK is used in the Android app.

Re: Android Mobile Crash report | signal 11 (SIGSEGV), code 1 (SEGV_MAPERR) question

slawek_michalik — Wed, 09 Oct 2019 08:07:02 GMT

Hi Patrick,

Seeing the Android architecture, it's what I suspected.

Thank you for your comment.

Regards,

Slawek