Enable crash keys for cast shell on android

chromecast/crash/android/cast_crash_reporter_client_android.cc

Index: chromecast/crash/android/cast_crash_reporter_client_android.cc
diff --git a/chromecast/crash/android/cast_crash_reporter_client_android.cc b/chromecast/crash/android/cast_crash_reporter_client_android.cc
index 2137faeea9bfcbca9b9d243efbda5cc4a13c9006..41717f892f8addde369c70fc0e0f8cb04b330ebf 100644
--- a/chromecast/crash/android/cast_crash_reporter_client_android.cc
+++ b/chromecast/crash/android/cast_crash_reporter_client_android.cc
@@ -11,6 +11,7 @@
 #include "chromecast/android/chromecast_config_android.h"
 #include "chromecast/common/global_descriptors.h"
 #include "chromecast/common/version.h"
+#include "chromecast/crash/cast_crash_keys.h"
 #include "content/public/common/content_switches.h"
 
 namespace chromecast {
@@ -55,6 +56,10 @@ bool CastCrashReporterClientAndroid::GetCrashDumpLocation(
   return true;
 }
 
+size_t CastCrashReporterClientAndroid::RegisterCrashKeys() {
+  return crash_keys::RegisterCastCrashKeys();

[byungchul, 2015/02/18 19:09:03]

Do you plan to do same for all products?

[kjoswiak, 2015/02/18 19:46:51]

This is in consideration. Part of the problem I've run into is our crash
handling on chromecast and android are very different.

Android uses mostly default chrome path, which means crash keys make a lot of
sense and are the cleanest way to take care of meta data, whereas chromecast has
its own mostly custom system for crash handling that circumnavigates crash keys,
and instead uses a custom system for tracking metadata.

One of these systems should probably converge to the other, but I'm not sure
which

+}
+
 bool CastCrashReporterClientAndroid::GetCollectStatsConsent() {
   return android::ChromecastConfigAndroid::GetInstance()->CanSendUsageStats();
 }