Skip to content

Commit 48eb26a

Browse files
committed
Highlight inproc macOS breakage
1 parent 1b641e1 commit 48eb26a

File tree

2 files changed

+2
-2
lines changed
  • docs/platforms/native

2 files changed

+2
-2
lines changed

docs/platforms/native/advanced-usage/backend-tradeoffs/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Both backends are comparable in how they differ from `crashpad`. However, there
4545
* `inproc`, on the other hand, uses signal handling on Linux and macOS (meaning you only get a `POSIX` compatibility layer over mach exception ports) and `UnhandledExceptionFilter` on Windows (solely errors registered by SEH)
4646
* as a result of choosing signal handling on macOS, `inproc` is currently broken on macOS since Apple eliminated unwinding from signal handlers
4747
* `inproc` is exceptionally lightweight and written entirely in C, meaning it does not rely on a weighty C++ runtime library, which is also more often affected by ABI incompatibilities
48-
* `breakpad` generates minidumps (like `crashpad` does), whereas `inproc` follows the Sentry event structure and primarily defers to the OS-provided unwinder and symbolication capabilities. Sentry can potentially extract more information from the provided minidump than simply a stack trace and registers. However, it also means that the crash context inside the minidump will be opaque until processed in the backend, whereas a local `relay` instance could process an entire `inproc`-event if required.
48+
* `breakpad` generates minidumps (like `crashpad` does), whereas `inproc` follows the Sentry event structure and primarily defers to the OS-provided unwinder and symbolication capabilities. Sentry can potentially extract more information from the provided minidump than simply a stack trace and registers. However, it also means that the crash context inside the minidump will be opaque until processed in the backend, whereas a local `relay` instance could process an entire `inproc` event if required.
4949

5050
### So when do I choose `inproc`?
5151

docs/platforms/native/configuration/backends/index.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ CMake option, with support for the following options:
1616
It is used as the default on Windows, macOS, and Linux.
1717
- `breakpad`: This uses the in-process breakpad handler.
1818
- `inproc`: A small in-process handler supported on all platforms
19-
and used as a default on Android.
19+
and used as a default on Android. It does no longer work on macOS since version 13 ("Ventura").
2020
- `none`: This builds `sentry-native` without a backend, so it does not handle
2121
crashes. It is primarily used for tests.
2222

0 commit comments

Comments
 (0)