tools/oom_dump/README - Issue 3170015: Initial implementation of oom_dump utility.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: tools/oom_dump/README

Issue 3170015: Initial implementation of oom_dump utility. (Closed)

Patch Set: Addressing Mads' comments Created 10 years, 4 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

OLD	NEW
(Empty)
	1 oom_dump extracts useful information from Google Chrome OOM minidumps.
	Mark Mentovai 2010/08/16 20:56:43 Extra space in "OOM minidumps." Extra space in "OOM minidumps." antonm 2010/08/17 13:13:19 Done. Show quoted text On 2010/08/16 20:56:43, Mark Mentovai wrote: > Extra space in "OOM minidumps." Done.
	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 link error when
	Mark Mentovai 2010/08/16 20:56:43 link error -> a link error link error -> a link error antonm 2010/08/17 13:13:19 Done. Show quoted text On 2010/08/16 20:56:43, Mark Mentovai wrote: > link error -> a link error Done.
	19 building oom_dump.

	20

	21 The last step is to build oom_dump itself. The following command should work:

	22

	23 cd <v8 working copy>/tools/oom_dump

	24 scons BREAKPAD_DIR=<path to google-breakpad working copy>

	25

	26 (Additionally you can control v8 working copy dir, but default---../..---
	Mark Mentovai 2010/08/16 20:56:43 Confusing! Confusing! antonm 2010/08/17 13:13:19 Just simplified it. Is it fine now? Show quoted text On 2010/08/16 20:56:43, Mark Mentovai wrote: > Confusing! Just simplified it. Is it fine now?
	27 should work just fine).

	28

	29 If everything goes fine, oom_dump <path to minidump> should print

	30 some useful information about OOM crash.
	Mark Mentovai 2010/08/16 20:56:43 about (the\|\|an) OOM crash. about (the\|\|an) OOM crash. antonm 2010/08/17 13:13:19 Done. Show quoted text On 2010/08/16 20:56:43, Mark Mentovai wrote: > about (the\|\|an) OOM crash. Done.
OLD	NEW

« no previous file with comments | « no previous file | tools/oom_dump/SConstruct » ('j') | tools/oom_dump/oom_dump.cc » ('J')