Guides

Crash Reporting for C++

Native C++ doesn't hand you a stack trace when it falls over. It hands you a memory dump, if you're lucky, and a pile of addresses that mean nothing until they're symbolicated against the exact build that crashed. That gap is where most C+

Access Violation Crashes (EXCEPTION_ACCESS_VIOLATION): What They Are and How to Fix Them

If you write native code long enough, EXCEPTION_ACCESS_VIOLATION becomes an old, unwelcome friend. It's the most common way a C++ program dies, it shows up as the cryptic code 0xC0000005, and on a good day it points you straight at a null pointer. On a bad

Stack Overflow Crashes: Why Your Program Ran Out of Stack (and How to Find Out Where)

Not the website. The crash. The one where your program is humming along and then dies instantly with no useful error, or on Windows, EXCEPTION_STACK_OVERFLOW and status code 0xC00000FD. Usually it means a function called itself one too many times. Sometimes it means you asked the stack to

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