<trclass="memdesc:a790cc793a96f090e848160f8d7757ce9"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Additional exception flags that further identify the exception, in operating system-specific values. <ahref="#a790cc793a96f090e848160f8d7757ce9">More...</a><br/></td></tr>
<trclass="memdesc:acfa95816daebbd4603b2423013761c05"><tdclass="mdescLeft"> </td><tdclass="mdescRight">An address, in the address space of the process that this minidump file contains a snapshot of, of another <aclass="el"href="structMINIDUMP__EXCEPTION.html"title="Information about an exception that occurred in the process. ">MINIDUMP_EXCEPTION</a>. This field is used for nested exceptions. <br/></td></tr>
<trclass="memdesc:a90415942a28bed1cf46a96866713423a"><tdclass="mdescLeft"> </td><tdclass="mdescRight">The address that caused the exception. <ahref="#a90415942a28bed1cf46a96866713423a">More...</a><br/></td></tr>
<trclass="memdesc:a29c7d61cd5eddf5c4f493bae40cd2679"><tdclass="mdescLeft"> </td><tdclass="mdescRight">The number of valid elements in <aclass="el"href="structMINIDUMP__EXCEPTION.html#a5a8ba606d8065108a3053c7bb339822a"title="Additional information about the exception, specific to the operating system and possibly the Excepti...">ExceptionInformation</a>. <br/></td></tr>
<trclass="memdesc:a5a8ba606d8065108a3053c7bb339822a"><tdclass="mdescLeft"> </td><tdclass="mdescRight">Additional information about the exception, specific to the operating system and possibly the <aclass="el"href="structMINIDUMP__EXCEPTION.html#ab6a3e2b22e571abef6c879eed52d292e"title="The top-level exception code identifying the exception, in operating system-specific values...">ExceptionCode</a>. <ahref="#a5a8ba606d8065108a3053c7bb339822a">More...</a><br/></td></tr>
<p>For macOS minidumps, this will be an <aclass="el"href="mach_8h.html#EXC_x">EXC_*</a> exception type, such as <code>EXC_BAD_ACCESS</code>. <code>EXC_CRASH</code> will not appear here for exceptions processed as <code>EXC_CRASH</code> 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 <aclass="el"href="structMINIDUMP__EXCEPTION.html#a5a8ba606d8065108a3053c7bb339822a"title="Additional information about the exception, specific to the operating system and possibly the Excepti...">ExceptionInformation</a>.</p>
<p>For Windows minidumps, this will be an <code>EXCEPTION_*</code> exception type, such as <code>EXCEPTION_ACCESS_VIOLATION</code>.</p>
<dlclass="section note"><dt>Note</dt><dd>This field is named ExceptionCode, but what is known as the “exception code” on macOS/Mach is actually stored in the <aclass="el"href="structMINIDUMP__EXCEPTION.html#a790cc793a96f090e848160f8d7757ce9"title="Additional exception flags that further identify the exception, in operating system-specific values...">ExceptionFlags</a> field of a minidump file.</dd></dl>
<dlclass="todo"><dt><b><aclass="el"href="todo.html#_todo000001">Todo:</a></b></dt><dd>Document the possible values by OS. There may be OS-specific enums in minidump_extensions.h. </dd></dl>
<li>For exception type <code>EXC_CRASH</code> generated from another preceding exception, the original exception code will appear here, not the code as received by the Mach exception handler.</li>
<li>For exception types <code>EXC_RESOURCE</code> and <code>EXC_GUARD</code>, the high 32 bits of the code received by the Mach exception handler will appear here.</li>
<p>In all cases for macOS minidumps, the code as it was received by the Mach exception handler will appear at index 1 of <aclass="el"href="structMINIDUMP__EXCEPTION.html#a5a8ba606d8065108a3053c7bb339822a"title="Additional information about the exception, specific to the operating system and possibly the Excepti...">ExceptionInformation</a>.</p>
<p>For Windows minidumps, this will either be <code>0</code> if the exception is continuable, or <code>EXCEPTION_NONCONTINUABLE</code> to indicate a noncontinuable exception.</p>
<dlclass="todo"><dt><b><aclass="el"href="todo.html#_todo000002">Todo:</a></b></dt><dd>Document the possible values by OS. There may be OS-specific enums in minidump_extensions.h. </dd></dl>
<p>Additional information about the exception, specific to the operating system and possibly the <aclass="el"href="structMINIDUMP__EXCEPTION.html#ab6a3e2b22e571abef6c879eed52d292e"title="The top-level exception code identifying the exception, in operating system-specific values...">ExceptionCode</a>. </p>
<p>For macOS minidumps, this will contain the exception type as received by a Mach exception handler and the values of the <code>codes[0]</code> and <code>codes[1]</code> (exception code and subcode) parameters supplied to the Mach exception handler. Unlike <aclass="el"href="structMINIDUMP__EXCEPTION.html#ab6a3e2b22e571abef6c879eed52d292e"title="The top-level exception code identifying the exception, in operating system-specific values...">ExceptionCode</a> and <aclass="el"href="structMINIDUMP__EXCEPTION.html#a790cc793a96f090e848160f8d7757ce9"title="Additional exception flags that further identify the exception, in operating system-specific values...">ExceptionFlags</a>, the values received by a Mach exception handler are used directly here even for the <code>EXC_CRASH</code>, <code>EXC_RESOURCE</code>, and <code>EXC_GUARD</code> exception types. For Windows, these are additional arguments (if any) as provided to <code>RaiseException()</code>. </p>
