3c528da94c
Fourth of 5 small patches to fix various breakpad issues found while testing dump_syms on DWARF v5 in ChromeOS. Dwarfv5 adds many new Type Unit sections to debug information. Since these only contain type information, they are of no interest to dump_syms. This CL gets dump_syms to skip trying to process the type unit sections. Without this CL, dump_syms takes ~ 3 hours to process the DWARF v5 Chrome binary. With this CL, dump_syms takes ~ 8 minutes to process the DWARF v5 Chrome binary (about the same time as it takes for DWARF v4). This CL also adds a test case to verify that type units are being skipped. Change-Id: Ie0bb2d675718f7041b8e9b3186ed44f80a3ad39c Reviewed-on: https://chromium-review.googlesource.com/c/breakpad/breakpad/+/2634549 Reviewed-by: Sterling Augustine <saugustine@google.com>
Breakpad
Breakpad is a set of client and server components which implement a crash-reporting system.
- Homepage
- Documentation
- Bugs
- Discussion/Questions: google-breakpad-discuss@googlegroups.com
- Developer/Reviews: google-breakpad-dev@googlegroups.com
- Tests:
- Coverage
Getting started (from master)
-
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
fetchtool from depot_tools to download all the source repos.fetch breakpad cd src -
Build the source.
./configure && makeYou 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.
To request change review
-
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 google-breakpad-dev@googlegroups.com always CC’d.