Add support for catching native crashes in WinUI3

[tipa]

Package

Sentry

.NET Flavor

.NET

.NET Version

8.0.2

OS

Windows

SDK Version

4.2.1

Self-Hosted Sentry Version

No response

Steps to Reproduce

1. Create WinUI3 / WinAppSDK app
2. Sentry.SentrySdk.CauseCrash(Sentry.CrashType.Native)

Expected Result

Crash is being reported to sentry.io

Actual Result

No crash is being reported (but app crashes with System.AccessViolationException: 'Attempted to read or write protected memory. This is often an indication that other memory is corrupt).
Happens both in debug as well as in Release mode

[bitsandfoxes]

Hey @tipa, thanks for raising this. Could you provide us with some debug logs from the SDK so we can see what's going on?

[tipa]

Sure, I see these logs before the crash, during initialization:

  Debug: Initializing Hub for Dsn: '...'.
  Debug: This looks like a standard JIT/AOT application build.
  Debug: Starting BackgroundWorker.
  Debug: Registering integration: 'AutoSessionTrackingIntegration'.
  Debug: BackgroundWorker Started.
  Debug: Registering integration: 'AppDomainUnhandledExceptionIntegration'.
  Debug: Registering integration: 'AppDomainProcessExitIntegration'.
  Debug: Registering integration: 'SentryDiagnosticListenerIntegration'.
   Info: DiagnosticSource Integration is disabled because tracing is disabled.
  Debug: Registering integration: 'SystemDiagnosticsMetricsIntegration'.
   Info: System.Diagnostics.Metrics Integration is disabled because no listeners are configured.

And then when I trigger the crash:

  Debug: Triggering a deliberate exception because SentrySdk.CauseCrash(CrashType.Native) was called
An unhandled exception of type 'System.AccessViolationException' occurred in Sentry.dll
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

You can reproduce it easily using this example: TestException.zip

[bitsandfoxes]

Thanks for the repro and logs! Much appreciated!