Sha256: a4e944b0a8aca990cdcddff564c8d96f7cc249127a8f2d44994211c8eee4348c
Contents?: true
Size: 1.03 KB
Versions: 3
Compression:
Stored size: 1.03 KB
Contents
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 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 default---../..--- should work just fine). If everything goes fine, oom_dump <path to minidump> should print some useful information about OOM crash.
Version data entries
3 entries across 3 versions & 1 rubygems
Version | Path |
---|---|
rednode-0.1.2 | ext/node/deps/v8/tools/oom_dump/README |
rednode-0.1.1 | ext/node/deps/v8/tools/oom_dump/README |
rednode-0.1.0 | ext/node/deps/v8/tools/oom_dump/README |