For Linux crash reporting, BugSplat recommends using Crashpad. Crashpad is the latest open source crash reporting tool built by Google and is the successor to the popular Breakpad crash reporter and allows you to submit minidumps to a configured URL after a crash occurs in your product.
The first step in integrating with Crashpad is to ensure that your system has all the required dependencies. These dependenices include
clang++. The following snippet will download and install all the dependencies on an Ubuntu system:
sudo apt-get install git
sudo apt-get install python
sudo apt-get install llvm
sudo apt-get install clang
Once you've built and integrated Crashpad you will need to ensure that your application is built with symbolic information and a build identifier. Symbolic information is required in order to map the stacktrace in the minidump to function names and line numbers in your application's source. A build identifier is required so that
minidump_stackwalkcan match modules loaded at runtime with the corresponding
When specifying the Crashpad libraries
libbase.amust be the last library argument specified otherwise your code will not compile.
If you are building with
clang++, specify the
-gflag to ensure the output executable contains symbolic information for debugging. Additionally when building with
clang++you must pass the
-Wl,--build-idargument in order to ensure the linker creates a build identifier in the output executable. The following script from myUbuntuCrasher demonstrates how to link the Crashpad libraries and output an executable with symbolic information using
clang++ -pthread $PROJECT_DIR/main.cpp \
$CRASHPAD_DIR/tools/dump_syms $PROJECT_DIR/out/$MODULE_NAME > $SYM_FILE
$CRASHPAD_DIR/tools/symupload $SYM_FILE "https://$BUGSPLAT_DATABASE.bugsplat.com/post/bp/symbol/breakpadsymbols.php?appName=$BUGSPLAT_APP_NAME&appVer=$BUGSPLAT_APP_VERSION"
It's important that you re-upload symbols each time you build your application otherwise BugSplat will not be able to generate function names and line numbers for the crash report. Symbols should be uploaded using a new version for every build to ensure that your crashes are processed quickly.
If you've set everything up correctly, your crash report should look like this:
Linux crash example