Refactor Android to use chrome_crashpad_handler
Instead of using crashpad's crashpad_handler, refactor Android to use
our own custom chrome_crashpad_handler (also used by macOS) and have it
also pass through the CrashpadHandlerMain entry point so that it picks
up any custom crashpad hooks we want to install.
CQ-DEPEND=CL:1707405
Bug: 973167
Change-Id: Id6d91a35ce12e547b4a7c92d07f869c96afae797
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1708838
Reviewed-by: Andrew Grieve <[email protected]>
Reviewed-by: Mark Mentovai <[email protected]>
Reviewed-by: Michael Spang <[email protected]>
Commit-Queue: Vlad Tsyrklevich <[email protected]>
Cr-Commit-Position: refs/heads/master@{#682364}
diff --git a/docs/android_native_libraries.md b/docs/android_native_libraries.md
index 6fe246c9..ce221d1 100644
--- a/docs/android_native_libraries.md
+++ b/docs/android_native_libraries.md
@@ -19,9 +19,9 @@
dump is requested (e.g. after a crash), a Crashpad handler process is started
to produce a dump.
* Chrome and ChromeModern (Android J through M):
- * libcrashpad_handler.so is a standalone executable containing all of the
- crash dumping code. It is stored compressed and extracted automatically by
- the system, allowing it to be directly executed to produce a crash dump.
+ * libchrome_crashpad_handler.so is a standalone executable containing all of
+ the crash dumping code. It is stored compressed and extracted automatically
+ by the system, allowing it to be directly executed to produce a crash dump.
* Monochrome (N through P) and SystemWebView (L through P):
* All of the Crashpad code is linked into the package's main native library
(e.g. libmonochrome.so). When a dump is requested, /system/bin/app_process