Closed Bug 764222 Opened 13 years ago Closed 11 years ago

More detailed "EMPTY:" error signatures

Categories

(Socorro :: Backend, task)

Product:
Socorro
Component:
Backend
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kairo, Assigned: lars)

Details

From our discussion today, the "EMPTY: no crashing thread identified; corrupt dump" error signature should be split into at least different one for zero minidumps and one for having stack info but not being able to identify the crashing thread.
Assignee: nobody → lars
Do we have an update on this?
This feature depends on the adoption of the json MSDW in the processors. We are poised to do this pending resolution of some issues regarding PII in the processed_crash. The json MDSW returns far more useful error messages than the version currently in use. The new stackwalker can return any of "ERROR_MINIDUMP_NOT_FOUND", "ERROR_NO_MINIDUMP_HEADER", "ERROR_NO_THREAD_LIST", "ERROR_GETTING_THREAD", "ERROR_GETTING_THREAD_ID", "SYMBOL_SUPPLIER_INTERRUPTED" as a status. If any of these messages are present, Socorro will append the message to the signature of the affected crash.
the json stackwalker is is use and new messages have been given to "empty" crashes. closeing as resolved. If that is not true, please reopen
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.