Open Bug 1711956 Opened 4 years ago Updated 4 years ago

Consider adding some mac_crash_info to crash signatures

Categories

(Socorro :: General, task)

Tracking

(Not tracked)

People

(Reporter: smichaud, Unassigned)

Details

As of bug 1577886, Socorro is now recording crashes with mac_crash_info. Bugs are being created that refer to this data (see bug 1711944). But there's currently no way to put any of it into crash signatures. So it's not easy to find these bug reports from (say) the topcrashers page at https://crash-stats.mozilla.org/.

mac_crash_info data is not uniform. Multiple fields can be present, and a single field can contain multiple lines. So we probably need to make specific rules about specific kinds of mac_crash_info data.

Take for example mac_crash_info data from the module /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib:

In this case the crucial data is the error number in the signature_string field -- for example '0xfffffff9', '0xfffffffc' or '0xe00002c2'. And the (raw) signature for crashes with this data always contains the string "gpusGenerateCrashLog". So we could (presumably) write a rule that whenever mac_crash_info data is available for a crash whose signature contains "gpusGenerateCrashLog", we should add the error number (from the end of its signature_string field) to that signature. We might also specify that this should only happen when the module name is "libGPUSupportMercury.dylib".

Once we get started, we can open new bugs for specific tasks, and make them all depend on this bug as a meta bug.

The description suggests it has an example, but there's no example there. Is there something missing?

Oops, sorry.

Actually, all the bugs currently dependent on bug 1711944 refer to bug reports that are relevant examples for what I'm talking about in comment #0.

For reference, here are three crash reports, one each for the different error numbers:

bp-c6c0875e-2087-419f-a741-4292a0210518
bp-ec24a856-754b-41de-868e-d47bc0210514
bp-339c4e1b-f1c6-4889-aadf-f73770210513

You need to log in before you can comment on or make changes to this bug.