1306678 - Add some end-to-end tests for crashing + symbols

Status: NEW

(Toolkit :: Crash Reporting, defect)

Description

[(not currently active) Ted Mielczarek]

We've got a bunch of tests that test crashing, and a bunch of tests for our symbol dumping code, but we don't actually have any tests that verify that we can usefully process a minidump that we've generated and get symbolicated frames out. gsvelto hit this in a bad way in bug 1264367, and it's a hassle to figure out after-the-fact.

I think at the very least what we'd want to do is run Firefox, intentionally crash it, then process the minidump with the minidump_stackwalk binary from tooltool and ensure that we are not missing symbols for any binaries from the Firefox package. For one step further, if we're crashing in a controlled way we could ensure that we have a known symbol on the crashing thread stack.

A follow-on improvement would be to run a test against Nightly/Release builds that have uploaded symbols, to automatically submit a crash to crash-stats and verify that it was processed properly and isn't missing symbols. (That's more involved.)

Comment 1

[Julien Cristau [:jcristau]]

Mass wontfix for bugs affecting firefox 52.