| commit | fb7ac48ff29ea964d93c9fa1f98c368bdaab705d | [log] [tgz] |
|---|---|---|
| author | Sadaf Ebrahimi <[email protected]> | Tue Aug 22 03:33:37 2023 +0000 |
| committer | Automerger Merge Worker <[email protected]> | Tue Aug 22 03:33:37 2023 +0000 |
| tree | 8bac0eef29fb27b0f8ba28f8aaa4dc8400b43107 | |
| parent | fe0b979764663486600861261cb885ba27aeb491 [diff] | |
| parent | d668033f29b32287c83ee25fac06f62372406dac [diff] |
Upgrade google-breakpad to 922d49bdfe3c92e5d35c406f87f2c354637a2f8b am: 8bac876145 am: c5a0c8e46e am: e6b2e13bd8 am: 0b812164b7 am: d668033f29 Original change: https://android-review.googlesource.com/c/platform/external/google-breakpad/+/2720095 Change-Id: Id854c5af5285fdbb50be3ef10b35ac55d600f98e Signed-off-by: Automerger Merge Worker <[email protected]>
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 PATH.
Create a new directory for checking out the source code (it must be named breakpad).
mkdir breakpad && cd breakpad
Run the 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_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).
Optionally, run tests.
make check
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.
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 protected] always CC’d.