Closed Bug 304768 Opened 19 years ago Closed 18 years ago

Search talkback reports by stack (not just top line of stack)

Categories

(mozilla.org :: Talkback Server & Webtool, task)

task
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jruderman, Assigned: jay)

Details

(Whiteboard: [sg:want P2] [quicksearch 2.0])

It should be possible to search for talkback reports with a given function
anywhere in the stack.  Currently, a "stack signature" search only searches the
top line of the stack.  This makes it hard to research crashes with "random"
addresses at the top of the stack.
See also bug 304769 for giving incidents with "random hex addresses" at the top
better signatures for automatic analysis.
Whiteboard: [sg:fix]
This is something that I've been thinking about doing for a while, so I am going
to see if I can figure out a good way to do this in the next version of the
Talkback query tools.
Status: NEW → ASSIGNED
Whiteboard: [sg:fix] → [sg:fix] [quicksearch 2.0]
Whiteboard: [sg:fix] [quicksearch 2.0] → [sg:want P2] [quicksearch 2.0]
Mostly fixed -- you can now search across the top 5 frames stack traces using http://talkback-public.mozilla.org/search/start.jsp.  Thanks, Jay!
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Thanks Jesse...  it's long overdue. ;-)

v.fixed.  Things seem to working ok with the limit set to the top 5 stack frames.  If anyone feels a need to increase that, we can look into it.  I think 5 is a good start and if we think increasing that to 10 will be better, we can do it...but I think that might return too much static.  

A better approach would be to combine searches for a given stack signature and a stack frame at a specified index in the stack...which is definitely possible.  If anyone thinks that might be good, please log a new bug and assign it to me. :-)

For now, you can now search for any part of the stack frame for the top 5...which include the function, source filenames (including the full path), and line numbers.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.