On 2/27/2014 3:42 PM, Benjamin Smedberg wrote: > >> Downloading minidumps and disassembling them takes a lot of time >> though; it'd be really great if we could integrate this into >> crash-stats, so that we can analyze dumps much faster. > > I filed bug 977778 on this. It's certainly not going to happen this > quarter but perhaps next quarter.
In the meantime, if you haven't been using the get-minidump-instructions tool[1], that's the simplest way to do this analysis. > >> I also found >> bug 627111 [1] to automatically categorize JIT crashes. If we could >> run that script every day and post the results as a graph somewhere it >> may be easier to detect new crashes. > It may be possible to do this classification automatically nowadays. > Ted, is there anything particularly expensive about that tool which > would prevent us from running it as part of the normal > json-minidump-stackwalk process? Then we can pretty easily write a > crash-stats classifier for it. That tool should be pretty cheap, it's just looking at the exception context, the memory mappings, and then disassembling the bytes around the faulting instruction pointer and looking for certain patterns. That ought to slot right into our Socorro architecture nowadays. Do note that the tool only produces useful results on x86 currently, since Breakpad only has a built-in x86 disassembler. -Ted 1. http://hg.mozilla.org/users/tmielczarek_mozilla.com/get-minidump-instructions/ _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
