|author||Snehasish Kumar <firstname.lastname@example.org>||Mon Dec 14 18:26:33 2020 -0800|
|committer||Joshua Peraza <email@example.com>||Tue Dec 15 17:14:09 2020 +0000|
Add a test to check debug information for split functions. With optimizations such as -fsplit-machine-functions (clang) and -freorder-blocks-and-partition (gcc), the function body may be discontiguous in the binary. Control flow between the parts are routed using jumps. This test ensures that breakpad consumes debuginfo generated by the -fsplit-machine-functions optimization and the line table for the cold function part is correct. Change-Id: I44d59704864ee940dd429c5249d5d793fe081d6a Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/2591951 Reviewed-by: Sterling Augustine <firstname.lastname@example.org> Reviewed-by: Joshua Peraza <email@example.com>
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 firstname.lastname@example.org always CC’d.