win crashpad: Enable capture of indirect stack data

components/crash/content/app/crashpad_win.cc

Index: components/crash/content/app/crashpad_win.cc
diff --git a/components/crash/content/app/crashpad_win.cc b/components/crash/content/app/crashpad_win.cc
index 6c45bf3a16f07d9ba67acb0cfdc3d365a40cbb80..419a0511279e14687fe6c706b82da98915737e3f 100644
--- a/components/crash/content/app/crashpad_win.cc
+++ b/components/crash/content/app/crashpad_win.cc
@@ -75,6 +75,14 @@ base::FilePath PlatformCrashpadInitialization(bool initial_client,
     base::FilePath exe_file;
     CHECK(PathService::Get(base::FILE_EXE, &exe_file));
 
+    bool is_per_user_install =
+        crash_reporter_client->GetIsPerUserInstall(exe_file);
+    if (crash_reporter_client->GetShouldDumpLargerDumps(is_per_user_install)) {
+      crashpad::CrashpadInfo::GetCrashpadInfo()
+          ->set_gather_indirectly_referenced_memory(

[Mark Mentovai, 2016/02/18 03:57:38]

It occurs to me that maybe we should have made this a property of the database’s
settings instead of something each process needs to decide on by itself.

+              crashpad::TriState::kEnabled);
+    }
+
     // If the handler is embedded in the binary (e.g. chrome, setup), we
     // reinvoke it with --type=crashpad-handler. Otherwise, we use the
     // standalone crashpad_handler.exe (for tests, etc.).