Move comment to license_note am: 6e0a3e409d am: 561e441fd6 am: 0b45cc4b21 am: f99aababb2

Original change: https://android-review.googlesource.com/c/platform/external/google-breakpad/+/2007327

Change-Id: I108c6bc04402cde920368013deb785d9f82b5aad
tree: b3439bb1623f4ff3c183e29e2492779da847c1b5
  1. .github/
  2. android/
  3. autotools/
  4. docs/
  5. m4/
  6. scripts/
  7. src/
  8. .gitignore
  9. .travis.yml
  10. aclocal.m4
  11. Android.bp
  12. Android.mk
  13. appveyor.yml
  14. AUTHORS
  15. breakpad-client.pc.in
  16. breakpad.pc.in
  17. ChangeLog
  18. configure
  19. configure.ac
  20. default.xml
  21. DEPS
  22. INSTALL
  23. LICENSE
  24. Makefile.am
  25. Makefile.in
  26. METADATA
  27. MODULE_LICENSE_BSD
  28. NEWS
  29. OWNERS
  30. PRESUBMIT.cfg
  31. README.ANDROID
  32. README.md
README.md

Breakpad

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

Getting started (from master)

  1. First, download depot_tools and ensure that they’re in your PATH.

  2. Create a new directory for checking out the source code (it must be named breakpad).

    mkdir breakpad && cd breakpad
    
  3. Run the fetch tool from depot_tools to download all the source repos.

    fetch breakpad
    cd src
    
  4. Build the source.

    ./configure && make
    

    You can also cd to another directory and run configure from there to build outside the source tree.

    This will build the processor tools (src/processor/minidump_stackwalk, src/processor/minidump_dump, etc), and when building on Linux it will also build the client libraries and some tools (src/tools/linux/dump_syms/dump_syms, src/tools/linux/md2core/minidump-2-core, etc).

  5. Optionally, run tests.

    make check
    
  6. Optionally, install the built libraries

    make install
    

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

To update an existing checkout to a newer revision, you can git pull as usual, but then you should run gclient sync to ensure that the dependent repos are up-to-date.

To request change review

  1. Follow the steps above to get the source and build it.

  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. Commit your changes to your local repo and upload them to the server. http://dev.chromium.org/developers/contributing-code e.g. git commit ... && git cl upload ... You will be prompted for credential and a description.

  4. At https://chromium-review.googlesource.com/ you'll find your issue listed; click on it, then “Add reviewer”, and enter in the code reviewer. Depending on your settings, you may not see an email, but the reviewer has been notified with google-breakpad-dev@googlegroups.com always CC’d.