mkrebs@chromium.org d80f175c1a Add optional file size limit for minidumps ... When there are upwards of 200 threads in a crashing process, each having an 8KB stack, this can result in a huge, 1.8MB minidump file. So I added a parameter that, if set, can compel the minidump writer to dump less stack. More specifically, if the writer expects to go over the limit (due to the number of threads), then it will dump less of a thread's stack after the first 20 threads. There are two ways to specify the limit, depending on how you write minidumps: 1) If you call WriteMinidump() directly, there's now a version of the function that takes the minidump size limit as an argument. 2) If you use the ExceptionHandler class, the MinidumpDescriptor object you pass to it now has a set_size_limit() method you would call before passing it to the constructor. BUG=chromium-os:31447, chromium:154546 TEST=Wrote a size-limit unittest; Ran unittests Review URL: https://breakpad.appspot.com/487002 git-svn-id: http://google-breakpad.googlecode.com/svn/trunk@1082 4c0a9323-5329-0410-9bdc-e9ce6186880e		2012-11-15 00:01:13 +00:00
..
client	Add optional file size limit for minidumps	2012-11-15 00:01:13 +00:00
common	Comment out unused arguments in definitions, as required by the Google C++ Style Guide.	2012-10-05 22:07:48 +00:00
google_breakpad	Allow processing dumps with missing stack memory for some threads	2012-11-06 16:50:01 +00:00
processor	Allow processing dumps with missing stack memory for some threads	2012-11-06 16:50:01 +00:00
third_party	Change an always true comparison to another conditional. Since	2012-09-17 21:55:37 +00:00
tools	Add custom implementation of NXGetArchInfoXXX to allow adding new arch.	2012-10-03 16:20:53 +00:00
breakpad_googletest_includes.h
config.h.in	Remove NetworkSourceLine{Resolver,Server} and related code. It never wound up being useful enough to use in production, so let's drop the maintenence burden	2011-07-07 20:53:52 +00:00