No description
Find a file
Scott Graham 88e5b2c880 win: Set LargeAddressAware on symupload
This was set manually on Chrome's built binary before
https://codereview.chromium.org/2173533002 but wasn't added to the build
file.

After this change:

c:\src\breakpad\src\src>dumpbin /headers tools\windows\symupload\Release\symupload.exe | grep large
                   Application can handle large (>2GB) addresses

This change only affects x86 builds.

R=mark@chromium.org
BUG=chromium:696911

Change-Id: I8f1bd5535af242edde51e70c60cf33b6170855ea
Reviewed-on: https://chromium-review.googlesource.com/447780
Reviewed-by: Mark Mentovai <mark@chromium.org>
2017-02-28 19:27:24 +00:00
android
autotools autotools: refresh config.{sub,guess} 2017-02-06 13:57:59 -05:00
docs Update links 2016-11-18 17:24:37 +00:00
m4 autotools: move -W flags to configure detection 2017-02-16 22:48:56 +00:00
scripts travis: add a clang build 2017-02-17 16:53:16 +00:00
src win: Set LargeAddressAware on symupload 2017-02-28 19:27:24 +00:00
.gitignore GitIgnore: Add dump_syms_mac 2016-11-14 20:16:05 +00:00
.travis.yml travis: add a clang build 2017-02-17 16:53:16 +00:00
aclocal.m4 autotools: move -W flags to configure detection 2017-02-16 22:48:56 +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 Switch to Gerrit for code reviews 2016-07-27 20:07:49 +00:00
configure autotools: move -W flags to configure detection 2017-02-16 22:48:56 +00:00
configure.ac autotools: move -W flags to configure detection 2017-02-16 22:48:56 +00:00
default.xml Upgrade google test to 1.8.0 2016-11-23 23:04:33 +00:00
DEPS Appveyor CI for Windows MSVS build 2017-02-13 17:57:15 +00:00
INSTALL
LICENSE
Makefile.am autotools: move -W flags to configure detection 2017-02-16 22:48:56 +00:00
Makefile.in autotools: move -W flags to configure detection 2017-02-16 22:48:56 +00:00
NEWS
README.ANDROID
README.md Appveyor CI for Windows MSVS build 2017-02-13 17:57:15 +00:00

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.