Implement Dump-on-DCHECK (via a new LogSeverity).

base/debug/dump_without_crashing.h

Index: base/debug/dump_without_crashing.h
diff --git a/base/debug/dump_without_crashing.h b/base/debug/dump_without_crashing.h
index b8ed17414ac571cddaf435ea978b3fd3e1bb811f..a5c85d5ebeace6991a98b1616d3b0c6c38c3dee1 100644
--- a/base/debug/dump_without_crashing.h
+++ b/base/debug/dump_without_crashing.h
@@ -17,7 +17,8 @@ namespace debug {
 // Before calling this function, call SetDumpWithoutCrashingFunction to pass a
 // function pointer, typically chrome!DumpProcessWithoutCrash.  See example code
 // in chrome_main.cc that does this for chrome.dll.
-BASE_EXPORT void DumpWithoutCrashing();
+// Returns false if called before SetDumpWithoutCrashingFunction.
+BASE_EXPORT bool DumpWithoutCrashing();

[Wez, 2016/12/19 23:57:46]

Some new call-sites have been introduced lately which Bind() this, assuming it
returns void.

Q: Would it be cleaner to add an explicit Dump1stTimeWithoutCrashing()?

Q: To ensure test reliability, should we also have ResetDump1stTimeForTest()?

 
 // Sets a function that'll be invoked to dump the current process when
 // DumpWithoutCrashing() is called.