Gitiles
Code Review Sign In
gerrit-public.fairphone.software / platform / external / google-breakpad / refs/heads/int/13/fp4
commitb7ba111e8c54beb68b59a59f424ffe42781ee293[log] [tgz]
authorColin Cross <ccross@android.com>Fri Mar 25 00:12:57 2022 +0000
committerAutomerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>Fri Mar 25 00:12:57 2022 +0000
treefb9ded0f62ba472ba9110b4d8347cbc60bb921da
parentf99aababb21288e6f4df9a4469a49416cbc236f2 [diff]
parent22cd171bf69d0357f283890a0dfb4431d2f2e9a9 [diff]
Tweak linux_glibc properties for musl builds in external/google-breakpad am: a58af67e6e am: f6df4ce36e am: 22cd171bf6

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

Change-Id: I900f50802d0f6036ba56439ac6ef297057fbd463
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
tree: fb9ded0f62ba472ba9110b4d8347cbc60bb921da
  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.