yuzu-emu/breakpad
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
No description
2152 commits 1 branch 0 tags 16 MiB
C++ 70.2%
Makefile 13.3%
C 5%
Shell 4.4%
Objective-C 3.1%
Other 4%
Find a file
Nathan Moinvaziri 225ed9172e Force dump_syms output to be checked out with LF line-ending. 
Otherwise, even with core.autocrlf=false, Windows will checkout these minidump output files with CRLF line-ending. It is necessary for these
files to be checked out using LF line-ending for the unit tests to pass.

Change-Id: I7cacf4b5fa56e007c8aa81202e0cef7ad42ae93a
Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/5160534
Reviewed-by: Ivan Penkov <ivanpe@chromium.org>
2024-01-03 20:53:15 +00:00
.github/workflows github: update to latest coverity scan action 2022-02-08 17:27:36 +00:00
android Update copyright boilerplate, 2022 edition (Breakpad) 2022-09-07 16:59:53 +00:00
autotools regen autotools 2022-06-30 06:44:14 +00:00
docs Add docs for INLINE and INLINE_ORIGIN in overview 2022-03-14 22:47:01 +00:00
m4 enables C++17 mode 2022-10-14 19:08:12 +00:00
src Add command line switch for reporting DWARF warnings. 2024-01-03 20:51:17 +00:00
.clang-format Add a .clang-format file to give us local control over Chromium style. 2020-08-31 18:46:34 +00:00
.gitattributes Force dump_syms output to be checked out with LF line-ending. 2024-01-03 20:53:15 +00:00
.gitignore gyp: drop unused build system 2022-12-05 01:38:54 +00:00
aclocal.m4 Fix warnings in configure.ac 2023-07-06 15:51:57 +00:00
appveyor.yml Appveyor CI for Windows MSVS build 2017-02-13 17:57:15 +00:00
AUTHORS
breakpad-client.pc.in
breakpad.pc.in
ChangeLog
codereview.settings codereview.settings: do not force squashing behavior 2019-08-14 17:56:21 +00:00
configure Add support for zstd compressed sections to dump_syms 2023-07-27 18:14:10 +00:00
configure.ac Add support for zstd compressed sections to dump_syms 2023-07-27 18:14:10 +00:00
default.xml gyp: drop unused build system 2022-12-05 01:38:54 +00:00
DEPS Update scripts to Python 3 2023-08-06 02:45:49 +00:00
DIR_METADATA add DIR_METADATA settings 2021-11-25 04:02:40 +00:00
INSTALL
LICENSE Update LICENSE file. 2023-01-27 20:35:32 +00:00
Makefile.am Add support for zstd compressed sections to dump_syms 2023-07-27 18:14:10 +00:00
Makefile.in Add support for zstd compressed sections to dump_syms 2023-07-27 18:14:10 +00:00
NEWS
OWNERS add OWNERS settings 2021-06-03 16:26:13 +00:00
README.ANDROID Update symbol file documentation links. 2016-06-10 06:29:06 -04:00
README.md CI: convert Travis to GH actions 2021-10-14 09:00:39 +00:00

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.