v8/tools/oom_dump
hpayer 59be4ba7f4 Reland "Merge old data and pointer space."
This reverts commit cbfcee5575.

BUG=

Review URL: https://codereview.chromium.org/1051233002

Cr-Commit-Position: refs/heads/master@{#27623}
2015-04-07 11:32:10 +00:00
..
oom_dump.cc Reland "Merge old data and pointer space." 2015-04-07 11:32:10 +00:00
README Update oom_dump README to indicate that people should build the correct V8 version. 2011-07-26 06:03:36 +00:00
SConstruct Initial implementation of oom_dump utility. 2010-08-16 12:36:02 +00:00

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.  Also, if you are testing against an older version of chrome
you should build the corresponding version of V8 to make sure that the type-id 
enum have the correct values.

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.