884267 - Enable crash reporting at runtime for all B2G builds (not just MOZILLA_OFFICIAL)

Status: RESOLVED DUPLICATE of bug 717538

(Firefox Build System :: General, defect)

Description

[(not currently active) Ted Mielczarek]

We had an issue where a partner had a Firefox OS release candidate build only to discover that crash reporting wasn't enabled. They didn't know about the (non-obvious) MOZILLA_OFFICIAL=1 build flag. This feels like the kind of thing we're going to run into again, so we should probably just enable crash reporting for all B2G builds regardless of MOZILLA_OFFICIAL.

We originally put this behind a flag because we were concerned about getting a flood of reports from self-made or unofficial builds. Nowadays our crash reporting volume is high enough that anything like that is a drop in the bucket anyway, and we have the tools in place to filter out bad crash reports if need be.

I think we probably want to limit this to B2G, only because the crash reporter can interfere with debugging on some platforms (OS X for sure). It shouldn't be an issue on Linux-based platforms.

Comment 1

[Robert Kaiser]

Note that to be able to differentiate crash reports coming in from custom builds (with "random" modifications) or official builds, we need bug 884273 before we do this default-enabling, so I'm setting this as a dependency.

Comment 2

[Joe Cheng [:jcheng] (please needinfo)]

leo+ so partners don't miss this in their final bulids
this was discussed over an email thread with b2g-drivers

Comment 3

[Alex Keybl [:akeybl]]

Already in the checklist, so removing this from leo+

Comment 4

[Robert Kaiser]

As bug 884273 is fixed now, we should do this as well. Who would do such a patch?

Comment 5

[Robert Kaiser]

IMHO, we should get this done at least in 1.2 to make it harder for partners to get things wrong.

Comment 6

[Robert Kaiser]

Hmm, and bug 717538 is pretty similar to this.

Comment 8

[Andrew Overholt [:overholt]]

Clearing koi?