Linux Linux logo for BugSplat
7 minute read

In a few simple steps, your application can be configured to send Linux crash reports to BugSplat.

Breakpad provides an Autotools build system that will build both the Linux client libraries and the processor libraries. Running ./configure && make in the Breakpad source directory will produce src/client/linux/libbreakpad_client.a, which contains all the code necessary to produce minidumps from an application.

For more information on Breakpad, see the Breakpad page and the the page which outlines configuring Breakpad to send Linux crashes (details below).

Before starting make sure to clone the Breakpad repo with Google Git.

Configuring Breakpad to send crash reports to BugSplat

Configure Breakpad to post crashes to https://[insert your database name here].bugsplat.com/post/bp/crash/postBP.php and make sure to specify your own value for the {database} portion of the URL, which corresponds to the BugSplat database used to store your crash reports.

Also, configure the Breakpad POST parameters prod for the BugSplat application name and version for the BugSplat application version. You can optionally specify values for the Breakpad POST parameters email and comments, which will be tracked with each crash report.

You can manually upload Breakpad crashes using our test page at www.bugsplat.com/post/bp/crash/Native. Viewing the source HTML of that page may help with Breakpad configuration.

The BugSplat database for your crash reports is created on the Databases page. Typically, you will create a new database for each major release of your product.

Breakpad symbol information must be uploaded to the BugSplat website to get symbolic stack reports. For Windows applications, symbols are extracted locally and uploaded using the Breakpad symupload utility. The symupload utility can be pointed at BugSplat using:

symupload exe_or_dll_file http://database.bugsplat.com/post/bp/symbol/breakpadsymbols.php?appName=MyApp&appVer=version

Be sure to specify your own values for the database, MyApp, and version parameters.

On other operating systems, you must first use the Breakpad dump_sym program to create symbol files, and then use the Breakpad symupload program to upload them. The symupload utility can be pointed at BugSplat using:

symupload symbol_file http://database.bugsplat.com/post/bp/symbol/breakpadsymbols.php?appName=MyApp&appVer=version

Be sure to specify your own values for the database, MyApp, and version parameters.

Extracted Breakpad symbols can be manually uploaded on our Breakpad Symbols page. Don’t use this page to upload Windows .exe or .dll files directly.

Remember that after each build you must upload new symbol files.

The final step is to test your application by forcing a crash. New crash reports will display immediately on the AllCrash page, and uploaded symbols can be seen on the Symbols page.