BugSplat 101

Interested in crash reporting but unsure of where to start? We'll guide you through the basics and let you know what to expect along the way.

Find Debug Fix Crashes image
Quick Start

Our 6-Step Guide for Getting Started With BugSplat

Interested in trying out BugSplat for yourself? Follow our 6-Step guide to quickly get BugSplat set up with your application.

Getting Started Guide
...
...
...

BugSplat's Critical Components Guides

Inside the Crash Report, Finding Your Most Critical Crashes, and Incorporating BugSplat Into Your Workflow.

The Anatomy of a Crash Report

BugSplat crash reports help developers with their mission to improve product stability and increase customer satisfaction. Below we break down precisely what is in a crash report to help give an understanding of the included data and why it is valuable. Read more →

Finding Your Most Critical Crashes

BugSplat automatically groups similar crashes to help you quickly identify bad defects using the top level of the call stack. This will help you easily find the handful of defects causing the majority of your crashes. Learn more →

The BugSplat Workflow Guide

Crash reporting can alter the balance between support and development, and swing it in your favor! Learn how to spend less time fixing your bugs and more time on new development - all while supporting a much more stable application. Learn more →

BugSplat Symbology

Getting high-fidelity symbolic call stacks.

symbol page screenshot

Guide to Symbol Uploads

Symbols files contain critical information that maps the data in a crash file to function names, file names and line numbers in your source code. Read more!

Deploying BugSplat

Read our guide to deploying BugSplat and get started fixing defects with real crash data. You'll likely find more crashes than you thought!