node/deps/v8/tools/oom_dump
Ben Noordhuis 70d1f32f56 deps: update v8 to 4.4.63.9
Upgrade the bundled V8 and update code in src/ and lib/ to the new API.

Notable backwards incompatible changes are the removal of the smalloc
module and dropped support for CESU-8 decoding.  CESU-8 support can be
brought back if necessary by doing UTF-8 decoding ourselves.

This commit includes https://codereview.chromium.org/1192973004 to fix
a build error on python 2.6 systems.  The original commit log follows:

    Use optparse in js2c.py for python compatibility

    Without this change, V8 won't build on RHEL/CentOS 6 because the
    distro python is too old to know about the argparse module.

PR-URL: https://github.com/nodejs/io.js/pull/2022
Reviewed-By: Rod Vagg <rod@vagg.org>
Reviewed-By: Trevor Norris <trev.norris@gmail.com>
2015-08-04 11:56:14 -07:00
..
oom_dump.cc deps: update v8 to 4.4.63.9 2015-08-04 11:56:14 -07:00
README Upgrade V8 to 3.5.3 2011-08-04 12:18:09 -07:00
SConstruct Upgrade V8 to 2.3.8 2010-08-17 08:37:25 -07: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.