Mirror of Google Breakpad project
Go to file
GlassOfWhiskey e69677e93d Added crash context float state flag
Instead of listing everywhere the set of architectures that do not
require/support explicit float state in their crash context, a new
GOOGLE_BREAKPAD_CRASH_CONTEXT_HAS_FLOAT_STATE preprocessor macro has
been defined.

Adding novel architectures will only require to manage the
macro definition in a single place.

Change-Id: I2732982f2cdfc9fcd2f71d6e5e122617faff9e82
Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/3876345
Reviewed-by: Mike Frysinger <vapier@chromium.org>
2022-09-07 12:28:57 +00:00
.github/workflows github: update to latest coverity scan action 2022-02-08 17:27:36 +00:00
android Added a missing dependency on android/google_breakpad/Android.mk 2022-06-28 16:28:24 +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 Only use O_CLOEXEC on platforms that support it 2017-05-10 21:32:37 +00:00
src Added crash context float state flag 2022-09-07 12:28:57 +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
.gitignore Add core_handler and pid2md into git ignore 2021-02-06 15:06:11 +00:00
aclocal.m4 regen autotools 2022-06-30 06:44:14 +00:00
appveyor.yml Appveyor CI for Windows MSVS build 2017-02-13 17:57:15 +00:00
AUTHORS
breakpad-client.pc.in make "make install" also install headers and pkgconfig files 2014-08-27 02:10:55 +00:00
breakpad.pc.in make "make install" also install headers and pkgconfig files 2014-08-27 02:10:55 +00:00
ChangeLog
codereview.settings codereview.settings: do not force squashing behavior 2019-08-14 17:56:21 +00:00
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 Update LSS dep to the last commit 2022-09-06 12:53:40 +00:00
DEPS Update LSS dep to the last commit 2022-09-06 12:53:40 +00:00
DIR_METADATA add DIR_METADATA settings 2021-11-25 04:02:40 +00:00
INSTALL
LICENSE There are source files with APSL-2.0 as well. 2020-07-17 01:32:59 +00:00
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 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

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 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.