gecko/toolkit/crashreporter/google-breakpad
Thomas Zimmermann d3c5f9848d Bug 809367 - Define ELFSIZE to 32 when building minidump_writer. r=ted
To update bionic to linaro/ics-plus-aosp we need to define ELFSIZE to 32
to make minidump_writer build.
2012-11-29 12:27:33 +01:00
..
android Merge the last PGO-green inbound changeset to m-c. 2012-09-25 17:30:17 -04:00
autotools bug 778364 - Update Breakpad to r1064. r=upstream 2012-10-08 10:16:09 -04:00
m4
src Bug 809367 - Define ELFSIZE to 32 when building minidump_writer. r=ted 2012-11-29 12:27:33 +01:00
aclocal.m4
AUTHORS
ChangeLog
codereview.settings
configure
configure.ac
COPYING
DEPS
INSTALL
Makefile.am
Makefile.in
NEWS
README
README.ANDROID
SVN-INFO bug 778364 - Update Breakpad to r1064. r=upstream 2012-10-08 10:16:09 -04:00

Breakpad is a set of client and server components which implement a
crash-reporting system.


-----
Getting started in 32-bit mode (from trunk)
Configure: CXXFLAGS=-m32 CFLAGS=-m32 CPPFLAGS=-m32 ./configure
    Build: make
     Test: make check
  Install: make install

If you need to reconfigure your build be sure to run "make distclean" first.


-----
To request change review:
0. Get access to a read-write copy of source.
   Owners at http://code.google.com/p/google-breakpad/ are able to grant
   this access.

1. Check out a read-write copy of source using instructions at
   http://code.google.com/p/google-breakpad/source/checkout

2. Make changes. Build and test your changes.
   For core code like processor use methods above.
   For linux/mac/windows, there are test targets in each project file.

3. Download http://codereview.appspot.com/static/upload.py

4. Run upload.py from the 'src' directory:
   upload.py --server=breakpad.appspot.com

   You will be prompted for credential and a description.

5. At http://breakpad.appspot.com you'll find your issue listed; click on it,
   and select Publish+Mail, and enter in the code reviewer and CC
   google-breakpad-dev@googlegroups.com

6. When applying code review feedback, specify the '-i' option when running
   upload.py again and pass the issue number so it updates the existing issue,
   rather than creating a new one.
   Be sure to rerun upload.py from the same directory as you did for previous
   uploads to allow for proper diff calculations.