Breakpad coverage for chrome_elf start up

chrome_elf/breakpad.h

Index: chrome_elf/breakpad.h
diff --git a/chrome_elf/breakpad.h b/chrome_elf/breakpad.h
new file mode 100644
index 0000000000000000000000000000000000000000..0c6ab272673cb7fe05683bad9d18ce671f549f59
--- /dev/null
+++ b/chrome_elf/breakpad.h
@@ -0,0 +1,32 @@
+// Copyright (c) 2014 The Chromium Authors. All rights reserved.
+// Use of this source code is governed by a BSD-style license that can be
+// found in the LICENSE file.
+
+#ifndef CHROME_ELF_BREAKPAD_H_
+#define CHROME_ELF_BREAKPAD_H_
+
+#include <windows.h>
+
+#include "breakpad/src/client/windows/handler/exception_handler.h"
+
+// Initializes collection and upload of crash reports. The caller has to ensure
+// that the user has agreed to crash dump reporting.

[robertshield, 2014/02/10 18:43:14]

How are we ensuring that the user has opted in to crash reporting?

[Cait (Slow), 2014/02/10 20:42:56]

Hrm..we currently don't. The remoting code I based this off of seems to check a
RegKey before setting up crash reporting -- should we be doing something
similar?

+//
+// Crash reporting has to be initialized as early as possible (e.g. the first
+// thing in main()) to catch crashes occuring during process startup.
+// Crashes which occur during the global static construction phase will not
+// be caught and reported. This should not be a problem as static non-POD
+// objects are not allowed by the style guide and exceptions to this rule are
+// rare.
+void InitializeCrashReporting();
+
+// Generates a crashdump for the provided |exinfo|. This crashdump will be
+// either be saved locally, or uploaded, depending on how the ExceptionHandler
+// has been configured.
+int GenerateCrashDump(EXCEPTION_POINTERS* exinfo);
+
+// Global pointer to the ExceptionHandler. This is initialized by
+// InitializeCrashReporting() and used by GenerateCrashDump() to record dumps.
+extern google_breakpad::ExceptionHandler* g_elf_breakpad;
+
+#endif  // CHROME_ELF_BREAKPAD_H_