Mark the app frames as `InApp` automatically for better issue grouping

[tustanivsky]

By default, crashes that are captured with sentry-native have all stack frames marked as non-in app (relevant for Windows, Linux, Android and consoles)

UE-specific default rules that were introduced earlier (https://github.com/getsentry/sentry-unreal/issues/669) help to handle this properly for assertions, ensures and non-fatal events but these don't affect crashes.

Here are stacktraces examples before/after adding stack.package:**/SentryPlayground* +app rule to a sample project (SentryPlayground is name of the game executable):

• Crash event without rule (all frames non-in app)
• Crash event with rule applied

For second event, system frames like RtlUserThreadStart, BaseThreadInitThunk etc. belong to threadbase category and excluded from in-app by stack trace rule category:threadbase -group v-group so in the end we get a proper callstack.

On Mac/iOS things work differently as sentry-cocoa does client-side stackwalking and marks frames as in-app at that stage.

Related to:

• https://github.com/getsentry/sentry/pull/85475
• https://github.com/getsentry/sentry/pull/99012

[linear[bot]]

UNREAL-78 Mark the app frames as `InApp` automatically for better issue grouping

[tustanivsky]

The Native SDK can be built with client-side stack unwinding enabled when using the crashpad backend (CMake parameter - CRASHPAD_ENABLE_STACKTRACE). The result is written to minidump file which is uploaded along with a captured crash event. It allows to get a human-readable stacktrace event when there were no debug symbols uploaded (example event). However, in editor this is not very helpful as callstack is populated with frames that do not point to actual code which causes a crash (editor example event).