Document AndroidOptions.SuppressSegfaults

[jamescrosswell]

See:

• Suppress Native SIGSEGV signal errors on Android #3903

[jamescrosswell]

Picking this up as a documentation task. Some context on how the landscape has shifted since this issue was filed, since SuppressSegfaults is no longer the only (or preferred) answer here.

The underlying problem — a single managed exception that surfaces as a native signal (e.g. a NullReferenceException raised as a SIGSEGV) gets captured twice: once as the managed .NET exception, once as a native crash. This is tracked in #3954.

The newer, preferred fix (@jpnurmi) reorders the signal handlers so the .NET runtime handles the managed exception first, preventing the duplicate at the source rather than suppressing the native signal:

• fix: prevent redundant native exceptions on Android/Mono #4676 — Android/Mono — opt-in via options.Native.ExperimentalOptions.SignalHandlerStrategy = SignalHandlerStrategy.ChainAtStart (experimental), shipped in 6.4.0
• fix: prevent redundant native exceptions on Android/CoreCLR #5127 — Android/CoreCLR — handled automatically (SDK keeps Default; ChainAtStart is only required on Mono), shipped in 6.4.1
• fix: prevent redundant native exceptions on iOS #5126 — iOS — handled automatically via an internal integration, no configuration required, shipped in 6.4.0

So the platform story is now:

• iOS — automatic since 6.4.0; there is no SuppressSegfaults option on iOS.
• Android — SignalHandlerStrategy.ChainAtStart is the preferred (experimental) fix; AndroidOptions.SuppressSegfaults (Suppress Native SIGSEGV signal errors on Android #3903) remains as a blunt fallback that suppresses SIGSEGV capture entirely (and can therefore hide genuine native segfaults).

Rather than documenting SuppressSegfaults in isolation, I've written this up as a "Duplicate events from native crashes" troubleshooting section that leads with the preferred fix per platform and keeps SuppressSegfaults as a documented Android fallback:

getsentry/sentry-docs#18623

Closing here once that merges. Flagging in case anyone thinks SuppressSegfaults should instead be deprecated now that ChainAtStart exists.