There's some information I've learned about reading crash reports, which is obvious now but wasn't when I was an intern many years ago, that isn't really covered by these.
Here's my workflow when looking at crashes: - Windows tells you if the exception occurred during a write or read. Look at the exception type. This is often the first thing I look at and important to keep in mind for the next step. - Look at the crashing source first, check the blame here and up the stack as well for a recent change. - Correlate the crash start date with the blame dates in the crashing stack and nearby. A strong match points to a regression that's easy to deal with if identified quickly. - Crash address can give you a hint as to what's going on: 0x0 -> null crash, 0x8 -> null offset accessing a member like this->mFoo, 0xfffffffffd8 -> accessing stack on some platforms, 0x80cdefd3 -> heap access, (the jemalloc poison values) - With the above look at the crash address distribution. Look at the exception type as well. If they are not all in the same bucket you *may* have a bad vtable or corruption occurring. Might want to do this per platform. - If you have a minidump see: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_a_minidump - If you don't have a minidump (non windows), and the line level info is insufficient, you can grab the instruction pointer and disassemble the binary. This will often tell you exactly what you were doing and which value is bad but is a bit tricky to follow with the optimizer. That's my rough workflow when looking at Soccoro. I'm leaving out the more specific searches like driver correlation for gfx crashers for instance. On Thu, May 26, 2016 at 9:52 AM, Benjamin Smedberg <benja...@smedbergs.us> wrote: > Here is a selection of docs that we've written over the years. Many are > incomplete. > > https://developer.mozilla.org/en-US/docs/Mozilla/Projects/Crash_reporting > https://developer.mozilla.org/en-US/docs/Crash_Data_Analysis > > https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/Debugging_a_minidump > > --BDS > > > On Wed, May 25, 2016 at 2:06 AM, Nicholas Nethercote < > n.netherc...@gmail.com > > wrote: > > > Hi, > > > > Do we have documentation on how to read crash reports? The only thing > > I have found is this page: > > > > https://support.mozilla.org/en-US/kb/helping-crashes > > > > which is not bad, but is lacking some details. I suspect there is > > quite a bit of crash report interpretation wisdom that is in various > > people's head, but not written down anywhere... > > > > Nick > > _______________________________________________ > > dev-platform mailing list > > dev-platform@lists.mozilla.org > > https://lists.mozilla.org/listinfo/dev-platform > > > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
