1.1 --- /dev/null Thu Jan 01 00:00:00 1970 +0000
1.2 +++ b/toolkit/crashreporter/google-breakpad/README Wed Dec 31 06:09:35 2014 +0100
1.3 @@ -0,0 +1,43 @@
1.4 +Breakpad is a set of client and server components which implement a
1.5 +crash-reporting system.
1.6 +
1.7 +
1.8 +-----
1.9 +Getting started in 32-bit mode (from trunk)
1.10 +Configure: CXXFLAGS=-m32 CFLAGS=-m32 CPPFLAGS=-m32 ./configure
1.11 + Build: make
1.12 + Test: make check
1.13 + Install: make install
1.14 +
1.15 +If you need to reconfigure your build be sure to run "make distclean" first.
1.16 +
1.17 +
1.18 +-----
1.19 +To request change review:
1.20 +0. Get access to a read-write copy of source.
1.21 + Owners at http://code.google.com/p/google-breakpad/ are able to grant
1.22 + this access.
1.23 +
1.24 +1. Check out a read-write copy of source using instructions at
1.25 + http://code.google.com/p/google-breakpad/source/checkout
1.26 +
1.27 +2. Make changes. Build and test your changes.
1.28 + For core code like processor use methods above.
1.29 + For linux/mac/windows, there are test targets in each project file.
1.30 +
1.31 +3. Download http://codereview.appspot.com/static/upload.py
1.32 +
1.33 +4. Run upload.py from the 'src' directory:
1.34 + upload.py --server=breakpad.appspot.com
1.35 +
1.36 + You will be prompted for credential and a description.
1.37 +
1.38 +5. At http://breakpad.appspot.com you'll find your issue listed; click on it,
1.39 + and select Publish+Mail, and enter in the code reviewer and CC
1.40 + google-breakpad-dev@googlegroups.com
1.41 +
1.42 +6. When applying code review feedback, specify the '-i' option when running
1.43 + upload.py again and pass the issue number so it updates the existing issue,
1.44 + rather than creating a new one.
1.45 + Be sure to rerun upload.py from the same directory as you did for previous
1.46 + uploads to allow for proper diff calculations.
