Crash Reporting with Google Crashpad
Crashpad is the crash handler under a huge amount of native software you already use. It's Google's cross-platform crash reporting system, the successor to Breakpad, and it's what catches the crash, writes a minidump, and ships it somewhere useful on Windows, macOS, Linux,
Crash Reporting for macOS
You know that macOS gives you crash logs. It does not give you a way to know that forty users hit the same crash last night, or which build it started in, or what your code was doing when it happened. The system writes a .crash file to a folder
Crash Reporting for Linux
Linux is where crash reporting gets quietly hard. Your users are on distributions you've never installed, with library versions you didn't test against, on hardware you've never seen. A core dump on a machine you can't access does you no good. You
Crash and Error Reporting for .NET
.NET fails in two different ways, and you want both covered. There's the hard crash, the process dies, often down in native or interop code, and there's the unhandled exception, the far more common case where something throws, a feature breaks, and the app limps on
Crash Reporting for Electron
Crash Reporting for Electron
Electron apps fail in two languages at once. There's the JavaScript layer, where you get exceptions and stack traces that look familiar. And there's the native layer underneath, the Chromium and Node internals, where a crash dumps a minidump that has nothing
Add BugSplat Crash Reporting to Your Monday.com Workflow
We're excited to announce that BugSplat's integration with Monday.com is live and brings a powerful combination of crash reporting and project management together, helping development teams work more efficiently and resolve issues faster.
