Closed Bug 588438 Opened 15 years ago Closed 15 years ago

[SkipList] Add mozalloc_abort and NS_DebugBreak_P to irrelevantSignatureRegEx

Categories

(mozilla.org Graveyard :: Server Operations, task)

task
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ted, Assigned: fox2mike)

Details

(Whiteboard: skiplist, needed for beta4)

mozalloc_abort and NS_DebugBreak_P are both functions that will show up at the top of the stack for any crash in which we intentionally abort the browser. They're not useful as signatures and should be skipped (in irrelevantSignatureRegEx).
Assignee: nobody → laura
Whiteboard: skiplist, needed for beta4
Target Milestone: --- → 1.8
Aravind: We will need to add to the end of the irrelevantSignatureRegEx the following, ie |mozalloc_abort?|NS_DebugBreak_P? The vertical bar is the delimiter between what is already there and the new bits. Before making this change in prod, can you please post the current skiplist config and diff to this bug for review?
Assignee: laura → server-ops
Component: Socorro → Server Operations
Product: Webtools → mozilla.org
QA Contact: socorro → mrz
Target Milestone: 1.8 → ---
Version: Trunk → other
Upping this so oncall gets it - needed done before 10am PT beta4 release.
Severity: normal → blocker
Assignee: server-ops → shyam
New version: irrelevantSignatureRegEx.default = '@0x[0-9a-fA-F]{2,}|@0x[1-9a-fA-F]|RaiseException|_CxxThrowException|Abort|___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___|_NSRaiseError|mozilla::ipc::RPCChannel::Call\(IPC::Message\*, IPC::Message\*\)'|mozalloc_abort|NS_DebugBreak_P
irrelevantSignatureRegEx.default = '@0x[0-9a-fA-F]{2,}|@0x[1-9a-fA-F]|RaiseException|_CxxThrowException|Abort|___TERMINATING_DUE_TO_UNCAUGHT_EXCEPTION___|_NSRaiseError|mozilla::ipc::RPCChannel::Call\(IPC::Message\*, IPC::Message\*\)|mozalloc_abort|NS_DebugBreak_P' That's been updated across 7 processors and they've all be restarted.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.