toolkit/crashreporter/google-breakpad/README

Wed, 31 Dec 2014 06:09:35 +0100

author
Michael Schloh von Bennewitz <michael@schloh.com>
date
Wed, 31 Dec 2014 06:09:35 +0100
changeset 0
6474c204b198
permissions
-rw-r--r--

Cloned upstream origin tor-browser at tor-browser-31.3.0esr-4.5-1-build1
revision ID fc1c9ff7c1b2defdbc039f12214767608f46423f for hacking purpose.

michael@0 1 Breakpad is a set of client and server components which implement a
michael@0 2 crash-reporting system.
michael@0 3
michael@0 4
michael@0 5 -----
michael@0 6 Getting started in 32-bit mode (from trunk)
michael@0 7 Configure: CXXFLAGS=-m32 CFLAGS=-m32 CPPFLAGS=-m32 ./configure
michael@0 8 Build: make
michael@0 9 Test: make check
michael@0 10 Install: make install
michael@0 11
michael@0 12 If you need to reconfigure your build be sure to run "make distclean" first.
michael@0 13
michael@0 14
michael@0 15 -----
michael@0 16 To request change review:
michael@0 17 0. Get access to a read-write copy of source.
michael@0 18 Owners at http://code.google.com/p/google-breakpad/ are able to grant
michael@0 19 this access.
michael@0 20
michael@0 21 1. Check out a read-write copy of source using instructions at
michael@0 22 http://code.google.com/p/google-breakpad/source/checkout
michael@0 23
michael@0 24 2. Make changes. Build and test your changes.
michael@0 25 For core code like processor use methods above.
michael@0 26 For linux/mac/windows, there are test targets in each project file.
michael@0 27
michael@0 28 3. Download http://codereview.appspot.com/static/upload.py
michael@0 29
michael@0 30 4. Run upload.py from the 'src' directory:
michael@0 31 upload.py --server=breakpad.appspot.com
michael@0 32
michael@0 33 You will be prompted for credential and a description.
michael@0 34
michael@0 35 5. At http://breakpad.appspot.com you'll find your issue listed; click on it,
michael@0 36 and select Publish+Mail, and enter in the code reviewer and CC
michael@0 37 google-breakpad-dev@googlegroups.com
michael@0 38
michael@0 39 6. When applying code review feedback, specify the '-i' option when running
michael@0 40 upload.py again and pass the issue number so it updates the existing issue,
michael@0 41 rather than creating a new one.
michael@0 42 Be sure to rerun upload.py from the same directory as you did for previous
michael@0 43 uploads to allow for proper diff calculations.

mercurial