Skip to content

fix(native): Honor system crash reporter forwarding#1743

Open
jpnurmi wants to merge 2 commits into
masterfrom
jpnurmi/fix/native/system-crash-reporter
Open

fix(native): Honor system crash reporter forwarding#1743
jpnurmi wants to merge 2 commits into
masterfrom
jpnurmi/fix/native/system-crash-reporter

Conversation

@jpnurmi
Copy link
Copy Markdown
Collaborator

@jpnurmi jpnurmi commented May 22, 2026

Add signal chaining before final crash termination, then use that handoff to honor system_crash_reporter_enabled on macOS.

This keeps the native backend compatible with previously installed Unix signal handlers while allowing macOS crashes to skip the system crash reporter by default. When system_crash_reporter_enabled is enabled, native forwards to the default signal path so the macOS system crash reporter can handle the crash.

For reference, what Crashpad does:

As a bonus, this also lays the groundwork for runtimes such as Mono/CoreCLR that rely on signal-chaining:

jpnurmi and others added 2 commits May 22, 2026 15:02
Restore the signal handlers that were installed before Sentry before
terminating after native crash processing. This lets runtimes and other crash
handlers observe the crash after Sentry captures it.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
Propagate system_crash_reporter_enabled into the native crash context and use it
on macOS after previous signal handlers have run. When disabled, exit without
re-raising so the system crash reporter is not invoked by default.

Co-Authored-By: OpenAI Codex <noreply@openai.com>
@jpnurmi jpnurmi force-pushed the jpnurmi/fix/native/system-crash-reporter branch from 4e69854 to c28f9a7 Compare May 22, 2026 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant