Closed
Bug 639445
Opened 13 years ago
Closed 7 years ago
improve signature handling and bug searching to handle symboless crashing frames
Categories
(Socorro :: General, task)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: timeless, Unassigned)
Details
Signature libc-2.11.2.so@0x75eea UUID e61ed929-ab7d-4e9a-a894-06c5c2110306 Time 2011-03-06 11:27:52.66888 Crashing Thread Frame Module Signature [Expand] Source 0 libc-2.11.2.so libc-2.11.2.so@0x75eea 1 seamonkey-bin nsAccUtils::GetRoleMapEntry accessible/src/base/nsAccUtils.cpp:656 2 seamonkey-bin nsAccessibilityService::GetAccessible accessible/src/base/nsAccessibilityService.cpp:1503 3 seamonkey-bin nsAccessibleTreeWalker::GetAccessible accessible/src/base/nsAccessibleTreeWalker.cpp:292 This stack trace should automatically find a bug with this summary: [Bug 639300] Whenever i use a javascript heavy online mail like aol or new yahoo mail seamonkey crashes [@ strcmp | nsAccUtils::GetRoleMapEntry ] The logic is roughly: 0. let search_string be empty (""); let the frame number be 0 1. if the crashing frame is in a module with symbols, go to 6 2. append ".*|\s*" to the search_string 3. get the next stack frame 4. if the frame depth exceeds limit give_up 5. go to 1 6. append the current frame to search_string 7. search for "[\s*@\s*"+search_string+"\s*]" ideally you end up with a search for: "[@.*|\s*nsAccUtils::GetRoleMapEntry\s*]" and it finds bug 639300 Ideally with this implemented the signature should also be changed eventually to something more meaningful based on this algorithm, but that can be done later.
Assignee | ||
Updated•13 years ago
|
Component: Socorro → General
Product: Webtools → Socorro
Comment 1•7 years ago
|
||
we've made a number of enhancements to both search and signature capabilities since then
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•