Sanitize mini- and microdumps for webview

components/crash/content/app/breakpad_linux.h

Index: components/crash/content/app/breakpad_linux.h
diff --git a/components/crash/content/app/breakpad_linux.h b/components/crash/content/app/breakpad_linux.h
index bbeb208b68e1a08e1376a279468e0cd0c1c30a0b..2cd1795831af5b2be7556be40513fb9ed2fe946a 100644
--- a/components/crash/content/app/breakpad_linux.h
+++ b/components/crash/content/app/breakpad_linux.h
@@ -36,6 +36,22 @@ extern void AddGpuFingerprintToMicrodumpCrashHandler(
 // generate dumps. Calling base::debug::DumpWithoutCrashing will still
 // generate a dump.
 extern void SuppressDumpGeneration();
+
+// Calling SetShouldSanitizeDumps determines whether or not subsequent
+// crash dumps should be sanitized. Sanitized dumps still contain
+// enough stack information to unwind crashes, but other stack data is
+// erased.
+extern void SetShouldSanitizeDumps(bool sanitize_dumps);
+
+// Inform breakpad of an address within the text section that is
+// considered interesting for the purpose of crashes so that this can
+// be used to elide microdumps that do not reference interesting
+// code. Minidumps will still be generated, but stacks from threads
+// that do not reference the principal mapping will not be included.
+// The full interesting address range is determined by looking up the
+// memory mapping that contains |addr|.
+extern void SetSkipDumpIfPrincipalMappingNotReferenced(
+    uintptr_t address_within_principal_mapping);
 #endif
 
 // Checks if crash reporting is enabled. Note that this is not the same as