They both are crashing report libraries that generates minidump for developer analyzing, and both are developed by Google's Chromium project:
Any difference in their intended use cases?
| / | Breakpad | Crashpad |
|---|---|---|
| OSX-10.10+/in-process | ✅ | ✅ |
| OSX-10.10+/out-process | ❌ | ✅ |
| / | Breakpad | Crashpad |
|---|---|---|
| iOS-5.0+/in-process | ✅ | ✅ |
| tvOS/in-process | ✅ | ❌ |
| watchOS/in-process | ✅ | ❌ |
Reply to @Lindeijer
See also the note in Breakpads documentation:
As opposed to Crashpad, Breakpad uses in-process crash reporting. This is less robust and has several disadvantages over out-of-process crash reporting. Unless you have integrated Breakpad already, we strongly recommend you to consider using Crashpad instead.
It is doc of Sentry, not doc of Breakpad
Actually Breakpad supports in-process and out-process on Windows/Linux/MacOSX(pre-10.10), according to https://chromium.googlesource.com/breakpad/breakpad/+/master/docs/exception_handling.md