Comment 2 for bug 1382233

Even if we don't use UnreportableReason to filter it'd still be useful to know apport's opinion of the bug report. We regularly see crashes that failed to retrace and contain the following in the retracer log file.

2015-11-03 10:58:59,824:19470:140298671347456:INFO:root:d54a5d64-8219-11e5-be9c-fa163e339c81:swift:Processing.
2015-11-03 10:59:00,046:19470:140298671347456:INFO:root:d54a5d64-8219-11e5-be9c-fa163e339c81:swift:Decompressing to /tmp/tmpS8eT8N-swift.d54a5d64-8219-11e5-be9c-fa163e339c81.oopsid.core
2015-11-03 10:59:00,188:19470:140298671347456:INFO:root:d54a5d64-8219-11e5-be9c-fa163e339c81:swift:Not a core dump per gdb.

apport does some checking of the core dump itself and if gdb is installed would add information like the following to the report.

 699 reason = 'Invalid core dump: ' + warnings.strip()
 700 self['UnreportableReason'] = reason

Having UnreportableReason in the Error Tracker would help us determine, in this specific case, if the core dump was already corrupt on the client or became corrupt during upload / saving to swift.

It'd also likely be useful in other cases that we aren't yet aware of.