Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(213)

Side by Side Diff: tools/oom_dump/README

Issue 7198021: Update oom_dump README to indicate that people should build the correct V8 version. (Closed) Base URL: http://v8.googlecode.com/svn/branches/bleeding_edge/
Patch Set: Created 9 years, 6 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch | Annotate | Revision Log
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
OLDNEW
1 oom_dump extracts useful information from Google Chrome OOM minidumps. 1 oom_dump extracts useful information from Google Chrome OOM minidumps.
2 2
3 To build one needs a google-breakpad checkout 3 To build one needs a google-breakpad checkout
4 (http://code.google.com/p/google-breakpad/). 4 (http://code.google.com/p/google-breakpad/).
5 5
6 First, one needs to build and install breakpad itself. For instructions 6 First, one needs to build and install breakpad itself. For instructions
7 check google-breakpad, but currently it's as easy as: 7 check google-breakpad, but currently it's as easy as:
8 8
9 ./configure 9 ./configure
10 make 10 make
11 sudo make install 11 sudo make install
12 12
13 (the catch: breakpad installs .so into /usr/local/lib, so you might 13 (the catch: breakpad installs .so into /usr/local/lib, so you might
14 need some additional tweaking to make it discoverable, for example, 14 need some additional tweaking to make it discoverable, for example,
15 put a soft link into /usr/lib directory). 15 put a soft link into /usr/lib directory).
16 16
17 Next step is to build v8. Note: you should build x64 version of v8, 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 18 if you're on 64-bit platform, otherwise you would get a link error when
19 building oom_dump. 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.
20 22
21 The last step is to build oom_dump itself. The following command should work: 23 The last step is to build oom_dump itself. The following command should work:
22 24
23 cd <v8 working copy>/tools/oom_dump 25 cd <v8 working copy>/tools/oom_dump
24 scons BREAKPAD_DIR=<path to google-breakpad working copy> 26 scons BREAKPAD_DIR=<path to google-breakpad working copy>
25 27
26 (Additionally you can control v8 working copy dir, but the default should work.) 28 (Additionally you can control v8 working copy dir, but the default should work.)
27 29
28 If everything goes fine, oom_dump <path to minidump> should print 30 If everything goes fine, oom_dump <path to minidump> should print
29 some useful information about the OOM crash. 31 some useful information about the OOM crash.
30 32
31 Note: currently only 32-bit Windows minidumps are supported. 33 Note: currently only 32-bit Windows minidumps are supported.
34
OLDNEW
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698