| OLD | NEW |
|---|
| (Empty) |
| 1 oom_dump extracts useful information from Google Chrome OOM minidumps. | |
| 2 | |
| 3 To build one needs a google-breakpad checkout | |
| 4 (http://code.google.com/p/google-breakpad/). | |
| 5 | |
| 6 First, one needs to build and install breakpad itself. For instructions | |
| 7 check google-breakpad, but currently it's as easy as: | |
| 8 | |
| 9 ./configure | |
| 10 make | |
| 11 sudo make install | |
| 12 | |
| 13 (the catch: breakpad installs .so into /usr/local/lib, so you might | |
| 14 need some additional tweaking to make it discoverable, for example, | |
| 15 put a soft link into /usr/lib directory). | |
| 16 | |
| 17 Next step is to build v8. Note: you should build x64 version of v8, | |
| 18 if you're on 64-bit platform, otherwise you would get a link error when | |
| 19 building oom_dump. Also, if you are testing against an older version of chrome | |
| 20 you should build the corresponding version of V8 to make sure that the type-id | |
| 21 enum have the correct values. | |
| 22 | |
| 23 The last step is to build oom_dump itself. The following command should work: | |
| 24 | |
| 25 cd <v8 working copy>/tools/oom_dump | |
| 26 scons BREAKPAD_DIR=<path to google-breakpad working copy> | |
| 27 | |
| 28 (Additionally you can control v8 working copy dir, but the default should work.) | |
| 29 | |
| 30 If everything goes fine, oom_dump <path to minidump> should print | |
| 31 some useful information about the OOM crash. | |
| 32 | |
| 33 Note: currently only 32-bit Windows minidumps are supported. | |
| OLD | NEW |
|---|
Chromium Code Reviews
Issue 2343423002:
Use git ls-tree to collect source files instead of walking the fs (Closed)
