Crash Reporting Guide for Firefox OS Partners
Mozilla has a world-class system for collecting, analyzing, and fixing crashes and other stability issues such as hangs. Firefox OS partners need to work with Mozilla to correctly enable crash reporting and upload symbols.
For general information about crash reporting, how it works, and how data is used, see the Crash reporting article.
It is essential that any device with Firefox branding have crash reporting enabled. This must be enabled by including the following line in the `mozconfig` file used to build the release build:
Crash reports contain key/value metadata and a minidump file. This file contains only the stack memory and memory mapping information, and does not contain any proprietary information such as symbols. Non-private data from crash reports are processed and displayed on crash-stats.mozilla.org. Because the actual minidump files may contain personal data if it is stored on the binary stack, these files remain private and are available only to Mozilla employees and certain partners who have a non-disclosure and privacy agreement for user data.
Symbol files allow Mozilla to process crash report minidumps. The symbol files are text files which are extracted from the binary debug information. For more information about the format of symbols files, see the breakpad documentation.
The symbols files for open-source code including all of gecko files must be available for crash processing. Partners should request an SSH account to upload symbols. See the symbol upload instructions for specific details. Symbols from multiple builds will not overwrite eachother on the server, because each symbol file is keyed against a unique debug identifier.
Firefox OS partners may also have binaries such as drivers which are not open-source. For Firefox OS partners as well as other partners such as plugin and extension vendors, Mozilla has a tool for encrypting symbol files so that they can still be used to produce backtraces and correlate crashes, without revealing the function or file names. Partners should take care that symbols for proprietary binaries are encrypted before being uploaded.
Qualcomm currently does not allow Firefox OS partners to upload Qualcomm-proprietary symbols, usually built from the vendor/qcom/proprietary subtree of the Firefox OS build. The symbols from this subtree should be archived, but at the present time they should not be uploaded to Mozilla.
While originally created for updates (displayed as "Update channel" in the Settings app under "Device Information" > "More Information" and available to use in the app.update.url preference of the prouct), the release channel plays an important role in determining what kind of build a crash comes from. Therefore, if you want to get useful crash statistics out of Mozilla's tools and want Mozilla's stability team to recognize and fix crashes, you need to set that channel according to the following rules:
- For release builds, the release channel should be set to release-<vendor>, e.g. release-zte, depending on the vendor that generates builds. Note that this is the same as update channel. If different (gecko) binaries are created for different regions, the region should be appended as well, e.g. release-zte-spain (or similar, the important point is release-<something> for release builds, in a way that the Mozilla stability can decipher the <something> part, and different channel names for individual builds that could be on the same device).
- For preview/pre-release/pre-certification builds, set the release channel to "nightly" on unstable of "beta" on stable/stabilization branches, and in case there's changes to binary code outside kernel/driver space, also add the vendor suffix, i.e. nightly-<vendor> or beta-<vendor>, following the release build model, in this case.
To set the channel, use the B2G_UPDATE_CHANNEL environment variable when building: