• R/O
  • HTTP
  • SSH
  • HTTPS

thirdparty-breakpad: Résumé du dépôt

Breakpad, a crash reporter, from Google.

Original home: https://chromium.googlesource.com/breakpad/breakpad/


Commits Récents RSS

Révision l'heure Auteur Message:
70914b2 2017-11-14 23:31:22 Mike Wittman master Make identical-code-folded symbol output more consistent ...
615ad2b 2017-11-14 04:50:29 Tomas Popela List missing 64-bit arches in the bundled curl Currently...
8a0edac 2017-11-08 08:24:48 Robert Sesek Add index-based set functionality to NonAllocatingMap. T...
3bbf3fb 2017-11-07 23:56:36 Peter Collingbourne dump_symbols: Stop rejecting files with Android packed re...
8e9080b 2017-11-04 02:06:05 Yi Wang Create LongStringDictionary and replace SimpleStringDicti...
550c622 2017-11-03 11:53:56 Adam Harrison Don’t set exit_after_write to false for tvOS. On tvOS, t...
5dad294 2017-11-03 02:56:17 Mark Mentovai Revert "Create LongStringDictionary and replace SimpleStr...
2d85d49 2017-11-02 11:40:39 Peter Collingbourne Rename an argument named "register" to "reg". This silen...
7e3c165 2017-10-31 02:23:56 Nicholas Baldwin Fix double declaration of tgkill when using Android NDK H...
fd0a0d2 2017-10-28 02:47:03 Yi Wang Create LongStringDictionary and replace SimpleStringDicti...

Branches

Nom Révision l'heure Auteur Message:
master 70914b2 2017-11-14 23:31:22 Mike Wittman Make identical-code-folded ...

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.

Afficher sur ancien navigateur de dépôt.