Conceived initially by Microsoft for crash reports on Windows, minidumps have become an accessible format for all sorts of native crashes. You can generate and upload minidumps yourself using Crashpad or Breakpad, use a higher-level SDK for platforms with built-in support for native crashes like Cocoa or Electron, and use them to triage issues with C++.
Collect native crash events in your issue stream, grouped by their crash location.
See detailed stack traces with resolved function names, file location, and CPU register values.
Assign issues to the engineers — or teams — who wrote the code that broke everything. (Obviously that would never, ever be you.)
Record environment and state details so you can recreate bugs, whether you’re targeting Windows, macOS, Linux, iOS, or Android.
Use Sentry’s tag distribution graph to isolate and prioritize any error by seeing how often it occurs in context.
- “How actionable is this error? Can I (please) just ignore it?”
- “Is the error isolated to users on Windows 10?”
- “How many splines were being reticulated?”
- “Was the power level over 9000?”
- “Did the waxing gibbous cause the problem?”
Event trails detail what the app was doing before any error occurred.
No WiFi? No problem-fi. Record events even when devices are offline or in airplane mode, then send errors as soon as connection is regained.
Is the problem actually not in your code at all, but instead maybe caused by something another team wrote that broke the API you’re using? Sentry can tell you that too.