|author||Michael Forney <firstname.lastname@example.org>||Mon Mar 16 23:47:53 2020|
|committer||Mike Frysinger <email@example.com>||Tue Mar 17 01:52:33 2020|
Roll src/src/third_party/lss/ f70e2f164..fd00dbbd0 (2 commits) https://chromium.googlesource.com/linux-syscall-support/+log/f70e2f1641e2..fd00dbbd0c06 $ git log f70e2f164..fd00dbbd0 --date=short --no-merges --format='%ad %ae %s' 2020-03-10 mforney Avoid conflict with getdents64 defined by libc 2019-01-26 vapier futex: change to 6 args Created with: roll-dep src/src/third_party/lss Bug: google-breakpad:631 Change-Id: Icc248237dcc7bdc3f7b74cd8556efcaf3b4b1c31 Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/2106526 Reviewed-by: Mike Frysinger <firstname.lastname@example.org>
Breakpad is a set of client and server components which implement a crash-reporting system.
First, download depot_tools and ensure that they’re in your
Create a new directory for checking out the source code (it must be named breakpad).
mkdir breakpad && cd breakpad
fetch tool from depot_tools to download all the source repos.
fetch breakpad cd src
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_dump, etc), and when building on Linux it will also build the client libraries and some tools (
Optionally, run tests.
Optionally, install the built libraries
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.
Follow the steps above to get the source and build it.
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.
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.
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 email@example.com always CC’d.