Update Crashpad to b4095401639ebe2ad33169e5c1d994065cbff1b8

third_party/crashpad/crashpad/handler/crashpad_handler.md

Index: third_party/crashpad/crashpad/handler/crashpad_handler.md
diff --git a/third_party/crashpad/crashpad/handler/crashpad_handler.md b/third_party/crashpad/crashpad/handler/crashpad_handler.md
index 30dacfe7eed641324072d87c5530a57d2bf40fbd..e76fed766f4c8a2eb7d86e2678469b30fcd15c73 100644
--- a/third_party/crashpad/crashpad/handler/crashpad_handler.md
+++ b/third_party/crashpad/crashpad/handler/crashpad_handler.md
@@ -138,6 +138,51 @@ establish the Crashpad client environment before running a program.
    service declared in a job’s `MachServices` dictionary (see launchd.plist(5)).
    The service name may also be completely unknown to the system.
 
+ * **--metrics-dir**=_DIR_
+
+   Metrics information will be written to _DIR_. This option only has an effect
+   when built as part of Chromium. In non-Chromium builds, and in the absence of
+   this option, metrics information will not be written.
+
+ * **--monitor-self**
+
+   Causes a second instance of the Crashpad handler program to be started,
+   monitoring the original instance for exceptions. The original instance will
+   become a client of the second one. The second instance will be started with
+   the same **--annotation**, **--database**, **--monitor-self-annotation**,
+   **--no-rate-limit**, **--no-upload-gzip**, and **--url** arguments as the
+   original one. The second instance will not be started with a
+   **--metrics-dir** argument even if the original instance was.
+
+   Where supported by the underlying operating system, the second instance will
+   be restarted should it exit before the first instance. The second instance
+   will not be eligible to be started asynchronously.
+
+ * **--monitor-self-annotation**=_KEY_=_VALUE_
+
+   Sets a module-level annotation mapping _KEY_ to _VALUE_ in the Crashpad
+   handler. This option may appear zero, one, or more times.
+
+   If **--monitor-self** is in use, the second instance of the Crashpad handler
+   program will find these annotations stored in the original instance and will
+   include them in any crash reports written for the original instance.
+
+   These annotations will only appear in crash reports written for the Crashpad
+   handler itself. To apply a process-level annotation to all crash reports
+   written by an instance of the Crashpad handler, use **--annotation** instead.
+
+ * **--monitor-self-argument**=_ARGUMENT_
+
+   When directed by **--monitor-self** to start a second instance of the
+   Crashpad handler program, the second instance will be started with _ARGUMENT_
+   as one of its arguments. This option may appear zero, one, or more times.
+   This option has no effect in the absence of **--monitor-self**.
+
+   This supports embedding the Crashpad handler into a multi-purpose executable
+   that dispatches to the desired entry point based on a command-line argument.
+   To prevent excessive accumulation of handler processes, _ARGUMENT_ must not
+   be `--monitor-self`.
+
  * **--no-rate-limit**
 
    Do not rate limit the upload of crash reports. By default uploads are