Initial implementation of oom_dump utility.

tools/oom_dump/README

Index: tools/oom_dump/README
diff --git a/tools/oom_dump/README b/tools/oom_dump/README
new file mode 100644
index 0000000000000000000000000000000000000000..5adbf65a0b999ba2bac29325cee2350b80ecb1ad
--- /dev/null
+++ b/tools/oom_dump/README
@@ -0,0 +1,30 @@
+oom_dump extracts useful information from Google Chrome OOM  minidumps.

[Mark Mentovai, 2010/08/16 20:56:43]

Extra space in "OOM  minidumps."

[antonm, 2010/08/17 13:13:19]

Done.

+
+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

[Mark Mentovai, 2010/08/16 20:56:43]

link error -> a link error

[antonm, 2010/08/17 13:13:19]

Done.

+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---../..---

[Mark Mentovai, 2010/08/16 20:56:43]

Confusing!

[antonm, 2010/08/17 13:13:19]

Just simplified it.  Is it fine now?

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

[Mark Mentovai, 2010/08/16 20:56:43]

about (the||an) OOM crash.

[antonm, 2010/08/17 13:13:19]

Done.