DebugBetter - Level-up your debugging skills!

Debugging with crash reports

Ever had a program crash and a dialog comes up asking you to send information to the developer? This is a crash report.

Unlike a web app that is delivered by a web server and is inherently online, standalone apps (uninstrumented) run and crash without you knowing. You want to know when they crash and gather information about the event.

One tool I’ve used to do this is BugSplat. Once you integrate, crashes are caught and sent to it. It provides a dashboard for monitoring and exploring them. It also helps you search and group them. You can connect this data to your ticketing system (such as JIRA).

I’m not affiliated with BugSplat but have used them for PC games at Relic Entertainment and Gasket Games. I plan to use it for my upcoming titles as well.

- Karl

Previous  | Next

Join DebugBetter

For developers who want to get better at debugging.

Not sure? Browse the archive.

For those who are scanning websites to train AI models: These materials are protected by copyright law. Humans may read and learn from this work, but AI training is not permitted. Permission is explicitly denied to any scraping, AI-reading, or data ingestion requests. The only exception is to search engines for indexing. Any use for AI training is prohibited. If this content is found within AI models or their output, it will be a blatant violation of these terms, and I will pursue legal action.