Not sure what you mean - the stack information is there, right? This is my workflow:
Search for all the MOZ_CRASHes (e.g., moz crash reason “exists” (sometimes I just search for the graphics reasons, but we don’t have the GFX prefix on all the crashes, so that doesn’t quite work all the time) Look at the top N signatures, pick one that looks like it could be graphics related See what the MOZ_CRASH string is for that particular crash Search for MOZ_CRASH reason that matches that string. Just in case it returns more than “other reports” DXR for the MOZ_CRASH reason - this gets me to the current version of the code, instead of the version specific one form the crash report itself. — - Milan > On Jun 1, 2016, at 10:13 , Andrew McCreight <amccrei...@mozilla.com> wrote: > > On Tue, May 31, 2016 at 7:14 PM, Nicholas Nethercote <n.netherc...@gmail.com >> wrote: > >> If you use your favourite source code search tool to look for >> "Shutdown too long", you'll find that this crash is occurring in >> toolkit/components/terminator/nsTerminator.cpp. For example, here's a >> DXR link: >> > > Sure, you can individually search for each assertion failure, but that's > not useful if you are just trying to skim the list looking for assertions > in code you are familiar with. The crash stack contains file information, > so it would be nice if that could be exposed somehow in a search. I don't > think you can do that right now, but I could be wrong. > > Andrew > _______________________________________________ > 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
