win: Capture some CRITICAL_SECTION debugging data

util/win/registration_protocol_win.h

Index: util/win/registration_protocol_win.h
diff --git a/util/win/registration_protocol_win.h b/util/win/registration_protocol_win.h
index 7c59bcdd38682ca8ec678a09bbc0b81247d04855..23428d7f41e032eae18b292ef2077de2edc54d6f 100644
--- a/util/win/registration_protocol_win.h
+++ b/util/win/registration_protocol_win.h
@@ -58,6 +58,14 @@ struct RegistrationRequest {
   //!     ExceptionInformation structure, used when handling a non-crashing dump
   //!     request.
   WinVMAddress non_crash_exception_information;
+
+  //! \brief The address, in the client process address space, of a

[Mark Mentovai, 2015/10/15 00:14:56]

Possessive on “process”.

[scottmg, 2015/10/15 18:22:23]

Done.

+  //!     `CRITICAL_SECTION` allocated with a valid .DebugInfo field. This can
+  //!     be accomplished by using the
+  //!     `RTL_CRITICAL_SECTION_FLAG_FORCE_DEBUG_INFO` flag to
+  //!     `InitializeCriticalSectionEx()`. This value can be `0`, however then
+  //!     limited lock data will be available in minidumps.
+  WinVMAddress critical_section_address;
 };
 
 //! \brief A message only sent to the server by itself to trigger shutdown.