Allow minidump_dump to print module lists that would normally be rejected
for being too long.
We've seen some minidumps that fail to process because they contain
a ridiculous number of modules (usually due to something leaking shm
mappings, it looks like). They're annoying to investigate because even
minidump_dump fails to load and print the module list. This patch makes
minidump_dump effectively remove the limit on the number of modules it
will load, so inspecting the dump by hand is possible.
R=vapier@chromium.org
Change-Id: I7a55387ca4aaad8664cd4d2651052da989366027
Reviewed-on: https://chromium-review.googlesource.com/957130
Reviewed-by: Mike Frysinger <vapier@chromium.org>

Getting started (from master)

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.

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.