On Fri, Feb 4, 2011 at 3:38 PM, Vyacheslav Egorov <[email protected]> wrote: > The first bug report :-) > > > Traceback (most recent call last): > File "tools/grokdump.py", line 835, in <module> > AnalyzeMinidump(options, args[0]) > File "tools/grokdump.py", line 823, in AnalyzeMinidump > heap_object.Print(Printer()) > File "tools/grokdump.py", line 614, in Print > p.Print("[%08d] = %s" % (i, self.ObjectField(offset))) > File "tools/grokdump.py", line 494, in __str__ > INSTANCE_TYPES[self.map.instance_type]) > KeyError: 167
Thanks! Fixed the bug and added support for the new JS_MESSAGE instance type. -- Vitaly > On Tue, Feb 1, 2011 at 3:33 PM, Vitaly Repeshko <[email protected]> wrote: >> Sample output: https://gist.github.com/805910 >> >> On Tue, Feb 1, 2011 at 5:33 PM, <[email protected]> wrote: >>> Reviewers: Vyacheslav Egorov, >>> >>> Description: >>> grokdump: Simple windows minidump analysis on linux. >>> >>> Analyses full minidump (.dmp) files. >>> >>> Shows the processor state at the point of exception including the >>> stack of the active thread and the referenced objects in the V8 >>> heap. Code objects are disassembled and the addresses linked from the >>> stack (pushed return addresses) are marked with "=>". >>> >>> Please review this at http://codereview.chromium.org/6312058/ >>> >>> Affected files: >>> A tools/disasm.py >>> A tools/grokdump.py >>> M tools/ll_prof.py >>> >>> >>> >> >> -- >> v8-dev mailing list >> [email protected] >> http://groups.google.com/group/v8-dev >> > > -- > v8-dev mailing list > [email protected] > http://groups.google.com/group/v8-dev > -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev
