Switch chrome_elf exception handling from breakpad to crashpad

blimp/engine/app/blimp_engine_crash_keys.cc

Index: blimp/engine/app/blimp_engine_crash_keys.cc
diff --git a/blimp/engine/app/blimp_engine_crash_keys.cc b/blimp/engine/app/blimp_engine_crash_keys.cc
index d858f50286808d84d5e46b60c9968601bf86ffe8..ae41595ab12f183434dd785e24586b9ad5c1329d 100644
--- a/blimp/engine/app/blimp_engine_crash_keys.cc
+++ b/blimp/engine/app/blimp_engine_crash_keys.cc
@@ -13,7 +13,9 @@ namespace engine {
 
 size_t RegisterEngineCrashKeys() {
   // For now these need to be kept relatively up to date with those in
-  // //chrome/common/crash_keys.cc::RegisterChromeCrashKeys()
+  // 1. //chrome/common/crash_keys.cc::RegisterChromeCrashKeys()
+  // 2. //chrome/app/chrome_crash_reporter_client_win.cc::
+  //    RegisterCrashKeysHelper()

[Wez, 2016/07/06 19:36:50]

We don't build the Blimp Engine for Windows, so I don't think we need this
comment?

[ananta, 2016/07/07 12:43:20]

Yes. While we don't build Blimp for Windows, the crash keys are mostly common
between all three files. I think the comment helps?

[Wez, 2016/07/08 22:54:09]

If they're "mostly common" then isn't staying up-to-date with the common
crash_keys.cc sufficient for the Blimp build?

If there were a chrome_crash_reporter_client[_posix].cc, for example, then it'd
be intuitive to refer to that here. Referring to a Windows-specific file is
confusing because presumably it is Windows-specific because its contents only
make sense on Windows, right?

[ananta, 2016/07/09 14:09:32]

Fair enough. Reverted the changes to the blimp_engine_crash_keys.cc file.

   // All of the keys used in //content and //components/crash must show up
   // here.
   // TODO(marcinjb): Change the approach when http://crbug.com/598854 is