chromeos: Initial support for crash reporting for chrome --mash

chrome/app/mash/BUILD.gn

Index: chrome/app/mash/BUILD.gn
diff --git a/chrome/app/mash/BUILD.gn b/chrome/app/mash/BUILD.gn
index bad668e61e77ada30fbd71905012a8ccae7fc8aa..a716123b223bd84c172fb8179097f83743f0c0c4 100644
--- a/chrome/app/mash/BUILD.gn
+++ b/chrome/app/mash/BUILD.gn
@@ -33,7 +33,18 @@ source_set("mash") {
   ]
 
   if (is_chromeos) {
-    deps += [ "//ash/resources" ]
+    sources += [
+      "mash_crash_reporter_client.cc",
+      "mash_crash_reporter_client.h",
+    ]
+    deps += [
+      "//ash/resources",
+      "//components/crash/content/app",
+      "//components/crash/core/common",
+      "//components/upload_list",
+      "//components/version_info:generate_version_info",
+      "//services/ui/gpu",

[James Cook, 2017/01/19 02:50:17]

Also, this is unfortunate. Any thoughts on how to handle crash keys, which need
to be used inside service code, but registered in a central location near main()
for crash reporting?

[sadrul, 2017/01/19 04:22:11]

Maybe use crash_keys::kActiveURL in chrome code instead?

I would use that key from mus-gpu too, but it brings in more dependencies, so
went with hardcoding the url instead. The crash-key owners were OK with it
(https://codereview.chromium.org/2622073005/#msg4)

[James Cook, 2017/01/19 18:01:18]

//chrome/app/mash is not supposed to depend on any code in //chrome - see
https://cs.chromium.org/chromium/src/chrome/app/mash/DEPS?type=cs&q=chrome/ap...

I'm going to remove the dep and hardcode the string instead, because crash_keys
owners were OK with that for your CL.

+    ]
   }
 
   if (is_linux && !is_android) {