Add and handle new dwarf5 string-related forms.

Adding the new forms by type and processing should avoid
the problems with 0c0e24f709288a129d665ec27d6f089189318385,
where new forms weren't handled in switch statements, breaking
the build.

Testing this should follow the testing for DW_FORM_GNU_str_index,
very closely, but there doesn't appear to be any tests for that,
or even DW_FORM_strp.

Change-Id: I609d56b1dc879971bfef1070f063f8457fec6017
Reviewed-by: Mike Frysinger <>
Reviewed-by: Mark Mentovai <>
3 files changed
tree: 01ad412d5a6d406959bf9763530f6b9026d1672f
  1. .github/
  2. .gitignore
  3. .travis.yml
  5. ChangeLog
  6. DEPS
  11. NEWS
  14. aclocal.m4
  15. android/
  16. appveyor.yml
  17. autotools/
  20. codereview.settings
  21. configure
  23. default.xml
  24. docs/
  25. m4/
  26. scripts/
  27. src/


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. e.g. git commit ... && git cl upload ... You will be prompted for credential and a description.

  4. At 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 always CC’d.