yuzu-emu/breakpad
1
0
Fork 0
mirror of https://github.com/yuzu-emu/breakpad.git synced 2024-11-24 05:25:37 +01:00
Code Issues Packages Projects Releases Wiki Activity
Mirror of Google Breakpad project
2,038 Commits 1 Branch 0 Tags 15 MiB
C++ 70.3%
Makefile 13.4%
C 5%
Shell 4.4%
Objective-C 3.1%
Other 3.7%
a7a8b9c300
Go to file
Zequan Wu a7a8b9c300 Fix int64_t format in fprintf by using PRIx64. 
Change-Id: Ic03ecc055c4eb097fbaaf8c8cd2c0a68d5aea8a0
Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/3826785
Reviewed-by: Joshua Peraza <jperaza@chromium.org>
2022-08-11 22:03:01 +00:00
.github/workflows
android
autotools regen autotools 2022-06-30 06:44:14 +00:00
docs
m4
src Fix int64_t format in fprintf by using PRIx64. 2022-08-11 22:03:01 +00:00
.clang-format
.gitignore
aclocal.m4 regen autotools 2022-06-30 06:44:14 +00:00
appveyor.yml
AUTHORS
breakpad-client.pc.in
breakpad.pc.in
ChangeLog
codereview.settings
configure configure: support rustc-demangle installations in the sysroot 2022-07-03 05:45:10 +00:00
configure.ac configure: support rustc-demangle installations in the sysroot 2022-07-03 05:45:10 +00:00
default.xml
DEPS
DIR_METADATA
INSTALL
LICENSE
Makefile.am {static_,}range_map: fix overflows under ubsan 2022-07-13 05:45:04 +00:00
Makefile.in {static_,}range_map: fix overflows under ubsan 2022-07-13 05:45:04 +00:00
NEWS
OWNERS
README.ANDROID
README.md

README.md

Breakpad

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

Getting started (from main)

  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.