win: Implement exception snapshot

compat/non_win/dbghelp.h

 // Copyright 2014 The Crashpad Authors. All rights reserved.
 //
 // Licensed under the Apache License, Version 2.0 (the "License");
 // you may not use this file except in compliance with the License.
 // You may obtain a copy of the License at
 //
 //     http://www.apache.org/licenses/LICENSE-2.0
 //
 // Unless required by applicable law or agreed to in writing, software
 // distributed under the License is distributed on an "AS IS" BASIS,
@@ skipping 392 matching lines @@
 struct __attribute__((packed, aligned(4))) MINIDUMP_EXCEPTION {
   //! \brief The top-level exception code identifying the exception, in
   //!     operating system-specific values.
   //!
   //! For Mac OS X minidumps, this will be an \ref EXC_x "EXC_*" exception type,
   //! such as `EXC_BAD_ACCESS`. `EXC_CRASH` will not appear here for exceptions
   //! processed as `EXC_CRASH` when generated from another preceding exception:
   //! the original exception code will appear instead. The exception type as it
   //! was received will appear at index 0 of #ExceptionInformation.
   //!
+  //! For Windows minidumps, this will be an \ref EXCEPTION_x "EXCEPTION_*"
+  //! exception type, such as `EXCEPTION_ACCESS_VIOLATION`.
+  //!
   //! \note This field is named ExceptionCode, but what is known as the
   //!     “exception code” on Mac OS X/Mach is actually stored in the
   //!     #ExceptionFlags field of a minidump file.
   //!
   //! \todo Document the possible values by OS. There may be OS-specific enums
   //!     in minidump_extensions.h.
   uint32_t ExceptionCode;
 
   //! \brief Additional exception flags that further identify the exception, in
   //!     operating system-specific values.
   //!
   //! For Mac OS X minidumps, this will be the value of the exception code at
   //! index 0 as received by a Mach exception handler, except:
   //!  * For exception type `EXC_CRASH` generated from another preceding
   //!    exception, the original exception code will appear here, not the code
   //!    as received by the Mach exception handler.
   //!  * For exception types `EXC_RESOURCE` and `EXC_GUARD`, the high 32 bits of
   //!    the code received by the Mach exception handler will appear here.
   //!
   //! In all cases for Mac OS X minidumps, the code as it was received by the
   //! Mach exception handler will appear at index 1 of #ExceptionInformation.
   //!
+  //! For Windows minidumps, this will either be `0` if the exception is
+  //! continuable, or `EXCEPTION_NONCONTINUABLE` to indicate a noncontinuable
+  //! exception.
+  //!
   //! \todo Document the possible values by OS. There may be OS-specific enums
   //!     in minidump_extensions.h.
   uint32_t ExceptionFlags;
 
   //! \brief An address, in the address space of the process that this minidump
   //!     file contains a snapshot of, of another MINIDUMP_EXCEPTION. This field
   //!     is used for nested exceptions.
   uint64_t ExceptionRecord;
 
   //! \brief The address that caused the exception.
   //!
   //! This may be the address that caused a fault on data access, or it may be
   //! the instruction pointer that contained an offending instruction.
   uint64_t ExceptionAddress;
 
   //! \brief The number of valid elements in #ExceptionInformation.
   uint32_t NumberParameters;
 
   uint32_t __unusedAlignment;
 
   //! \brief Additional information about the exception, specific to the
   //!     operating system and possibly the #ExceptionCode.
   //!
   //! For Mac OS X minidumps, this will contain the exception type as received
   //! by a Mach exception handler and the values of the `codes[0]` and
   //! `codes[1]` (exception code and subcode) parameters supplied to the Mach
   //! exception handler. Unlike #ExceptionCode and #ExceptionFlags, the values
   //! received by a Mach exception handler are used directly here even for the
   //! `EXC_CRASH`, `EXC_RESOURCE`, and `EXC_GUARD` exception types.
+
+  //! For Windows, these are additional arguments (if any) as provided to
+  //! `RaiseException()`.
   uint64_t ExceptionInformation[EXCEPTION_MAXIMUM_PARAMETERS];
 };
 
 //! \brief Information about the exception that triggered a minidump file’s
 //!     generation.
 struct __attribute__((packed, aligned(4))) MINIDUMP_EXCEPTION_STREAM {
   //! \brief The ID of the thread that caused the exception.
   //!
   //! \sa MINIDUMP_THREAD::ThreadId
   uint32_t ThreadId;
@@ skipping 370 matching lines @@
   //!  - A MINIDUMP_MODULE_LIST stream. All loaded modules are present.
   //!  - Typically, a MINIDUMP_MEMORY_LIST stream containing duplicate pointers
   //!    to the stack memory regions also referenced by the MINIDUMP_THREAD_LIST
   //!    stream. This type of minidump file also includes a
   //!    MINIDUMP_MEMORY_DESCRIPTOR containing the 256 bytes centered around
   //!    the exception address or the instruction pointer.
   MiniDumpNormal = 0x00000000,
 };
 
 #endif  // CRASHPAD_COMPAT_NON_WIN_DBGHELP_H_