GitLab

The loaded module key is set the first time a dynamic module is loaded
and never cleared (i.e. it signifies, "has this ever been loaded"),
whereas the active module key is cleared when the dynamic module is
unloaded (i.e. it signifies, "is this currently in use").

Because these key values can change at runtime (in contrast to
BuildInfo information), add a CrashKeys class that can store the
information before the native library has been loaded (where the pure
Java exception reporter will log it manually) and forward it to the
native side afterwards, where Breakpad will automatically take care of
uploading them.

Bug: TBD
Change-Id: Ib67ce32e18dfc8b93be18ff87da06ceeaa450fef
Reviewed-on: https://chromium-review.googlesource.com/1193867Reviewed-by: Peter Wen <wnwen@chromium.org>
Reviewed-by: Michael van Ouwerkerk <mvanouwerkerk@chromium.org>
Commit-Queue: Bernhard Bauer <bauerb@chromium.org>
Cr-Commit-Position: refs/heads/master@{#587317}