v8/oom_dump at 16a34196505f6b050cb076045ab43de319ecccd7 - v8

History

antonm@chromium.org 7bf19e80cd Various improvements to oom_dump and instance type lists. 1) addresses various Mark's concern; 2) adds some missing instance types and rearranges existing ones to follow InstanceType order; 3) various minor cleanups. Review URL: http://codereview.chromium.org/3119023 git-svn-id: http://v8.googlecode.com/svn/branches/bleeding_edge@5286 ce2b1a6d-e550-0410-aec6-3dcde31c8c00		2010-08-17 13:48:03 +00:00
..
oom_dump.cc	Various improvements to oom_dump and instance type lists.	2010-08-17 13:48:03 +00:00
README	Various improvements to oom_dump and instance type lists.	2010-08-17 13:48:03 +00:00
SConstruct	Initial implementation of oom_dump utility.	2010-08-16 12:36:02 +00:00

README

oom_dump extracts useful information from Google Chrome OOM minidumps.

To build one needs a google-breakpad checkout
(http://code.google.com/p/google-breakpad/).

First, one needs to build and install breakpad itself. For instructions
check google-breakpad, but currently it's as easy as:

  ./configure
  make
  sudo make install

(the catch: breakpad installs .so into /usr/local/lib, so you might
need some additional tweaking to make it discoverable, for example,
put a soft link into /usr/lib directory).

Next step is to build v8.  Note: you should build x64 version of v8,
if you're on 64-bit platform, otherwise you would get a link error when
building oom_dump.

The last step is to build oom_dump itself.  The following command should work:

  cd <v8 working copy>/tools/oom_dump
  scons BREAKPAD_DIR=<path to google-breakpad working copy>

(Additionally you can control v8 working copy dir, but the default should work.)

If everything goes fine, oom_dump <path to minidump> should print
some useful information about the OOM crash.

Note: currently only 32-bit Windows minidumps are supported.