Closed Bug 907312 Opened 7 years ago Closed 1 year ago
Report: stackwalking success/failure
I'd like a report to help identify the success rate of stackwalking and reasons why stackwalking might fail. jMDSW can be expanded to produce output on how it performed stackwalking: * exact frame walk via symbols * exact frame walk via frame pointer * guessed frame walk via frame pointer * guessed frame walk via scanning - extra data = scan size (there may be other reasons) It would be good to report on the total rate of successful stackwalk (back to main or threadstart). It is also important to know which DLLs are missing symbols, so that we can identify which external parties we need to push on to receive symbols, or worse whether we have symbol issues with Mozilla binaries.
We'll need to expose the frame trust values first. There's also a "modules missing symbols" list available nowadays as a result of processing, we could surface that.
Depends on: 638204
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.