Mirror of Google Breakpad project
Go to file
Sterling Augustine 428a01e8de There are source files with APSL-2.0 as well.
Change-Id: I3640ee9374732e9e308c6264c702c9af942e85b3
Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/2303999
Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2020-07-17 01:32:59 +00:00
.github
android Use breakpad_getcontext on all Linux platforms missing getcontext 2020-03-16 21:27:07 +00:00
autotools
docs
m4
scripts
src fix NDEBUG breakage with new dwarf5 code 2020-07-16 03:04:43 +00:00
.gitignore Add google_crashdump_uploader_test to .gitignore 2020-03-11 11:50:39 +00:00
.travis.yml
aclocal.m4
appveyor.yml
AUTHORS
breakpad-client.pc.in
breakpad.pc.in
ChangeLog
codereview.settings
configure Use breakpad_getcontext on all Linux platforms missing getcontext 2020-03-16 21:27:07 +00:00
configure.ac Use breakpad_getcontext on all Linux platforms missing getcontext 2020-03-16 21:27:07 +00:00
default.xml Roll src/src/third_party/lss/ f70e2f164..fd00dbbd0 (2 commits) 2020-03-17 01:52:33 +00:00
DEPS Roll src/src/third_party/lss/ f70e2f164..fd00dbbd0 (2 commits) 2020-03-17 01:52:33 +00:00
INSTALL
LICENSE There are source files with APSL-2.0 as well. 2020-07-17 01:32:59 +00:00
Makefile.am Use breakpad_getcontext on all Linux platforms missing getcontext 2020-03-16 21:27:07 +00:00
Makefile.in Use breakpad_getcontext on all Linux platforms missing getcontext 2020-03-16 21:27:07 +00:00
NEWS
README.ANDROID
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 theyre 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 CCd.