Describes an exception.
Syntax
typedef struct _EXCEPTION_RECORD {
DWORD ExceptionCode;
DWORD ExceptionFlags;
struct _EXCEPTION_RECORD *ExceptionRecord;
PVOID ExceptionAddress;
DWORD NumberParameters;
ULONG_PTR ExceptionInformation[EXCEPTION_MAXIMUM_PARAMETERS];
} EXCEPTION_RECORD;
Members
ExceptionCode
The reason the exception occurred. This is the code generated by a hardware exception, or the code specified in the
RaiseException function for a software-generated exception. The following tables describes the exception codes that are likely to occur due to common programming errors.
Value |
Meaning |
- EXCEPTION_ACCESS_VIOLATION
|
The thread tried to read from or write to a virtual address for which it does not have the appropriate access.
|
- EXCEPTION_ARRAY_BOUNDS_EXCEEDED
|
The thread tried to access an array element that is out of bounds and the underlying hardware supports bounds checking.
|
- EXCEPTION_BREAKPOINT
|
A breakpoint was encountered.
|
- EXCEPTION_DATATYPE_MISALIGNMENT
|
The thread tried to read or write data that is misaligned on hardware that does not provide alignment. For example, 16-bit values must be aligned on 2-byte boundaries; 32-bit values on 4-byte boundaries, and so on.
|
- EXCEPTION_FLT_DENORMAL_OPERAND
|
One of the operands in a floating-point operation is denormal. A denormal value is one that is too small to represent as a standard floating-point value.
|
- EXCEPTION_FLT_DIVIDE_BY_ZERO
|
The thread tried to divide a floating-point value by a floating-point divisor of zero.
|
- EXCEPTION_FLT_INEXACT_RESULT
|
The result of a floating-point operation cannot be represented exactly as a decimal fraction.
|
- EXCEPTION_FLT_INVALID_OPERATION
|
This exception represents any floating-point exception not included in this list.
|
- EXCEPTION_FLT_OVERFLOW
|
The exponent of a floating-point operation is greater than the magnitude allowed by the corresponding type.
|
- EXCEPTION_FLT_STACK_CHECK
|
The stack overflowed or underflowed as the result of a floating-point operation.
|
- EXCEPTION_FLT_UNDERFLOW
|
The exponent of a floating-point operation is less than the magnitude allowed by the corresponding type.
|
- EXCEPTION_ILLEGAL_INSTRUCTION
|
The thread tried to execute an invalid instruction.
|
- EXCEPTION_IN_PAGE_ERROR
|
The thread tried to access a page that was not present, and the system was unable to load the page. For example, this exception might occur if a network connection is lost while running a program over the network.
|
- EXCEPTION_INT_DIVIDE_BY_ZERO
|
The thread tried to divide an integer value by an integer divisor of zero.
|
- EXCEPTION_INT_OVERFLOW
|
The result of an integer operation caused a carry out of the most significant bit of the result.
|
- EXCEPTION_INVALID_DISPOSITION
|
An exception handler returned an invalid disposition to the exception dispatcher. Programmers using a high-level language such as C should never encounter this exception.
|
- EXCEPTION_NONCONTINUABLE_EXCEPTION
|
The thread tried to continue execution after a noncontinuable exception occurred.
|
- EXCEPTION_PRIV_INSTRUCTION
|
The thread tried to execute an instruction whose operation is not allowed in the current machine mode.
|
- EXCEPTION_SINGLE_STEP
|
A trace trap or other single-instruction mechanism signaled that one instruction has been executed.
|
- EXCEPTION_STACK_OVERFLOW
|
The thread used up its stack.
|
Another exception code is likely to occur when debugging console processes. It does not arise because of a programming error. The DBG_CONTROL_C exception code occurs when CTRL+C is input to a console process that handles CTRL+C signals and is being debugged. This exception code is not meant to be handled by applications. It is raised only for the benefit of the debugger, and is raised only when a debugger is attached to the console process.
ExceptionFlags
This member contains zero or more exception flags. The following table describes some of the commonly seen exception flags. Exception flags not present in the following table should be treated as reserved for system use.
Exception flag |
Meaning |
- EXCEPTION_NONCONTINUABLE
|
The presence of this flag indicates that the exception is a noncontinuable exception, whereas the absence of this flag indicates that the exception is a continuable exception.
Any attempt to continue execution after a noncontinuable exception causes the EXCEPTION_NONCONTINUABLE_EXCEPTION exception.
|
- EXCEPTION_SOFTWARE_ORIGINATE
|
This flag is reserved for system use.
|
ExceptionRecord
A pointer to an associated
EXCEPTION_RECORD structure. Exception records can be chained together to provide additional information when nested exceptions occur.
ExceptionAddress
The address where the exception occurred.
NumberParameters
The number of parameters associated with the exception. This is the number of defined elements in the ExceptionInformation array.
ExceptionInformation[EXCEPTION_MAXIMUM_PARAMETERS]
An array of additional arguments that describe the exception. The
RaiseException function can specify this array of arguments. For most exception codes, the array elements are undefined. The following table describes the exception codes whose array elements are defined.
Exception code |
Meaning |
- EXCEPTION_ACCESS_VIOLATION
|
The first element of the array contains a read-write flag that indicates the type of operation that caused the access violation. If this value is zero, the thread attempted to read the inaccessible data. If this value is 1, the thread attempted to write to an inaccessible address.
If this value is 8, the thread caused a user-mode data execution prevention (DEP) violation.
The second array element specifies the virtual address of the inaccessible data.
|
- EXCEPTION_IN_PAGE_ERROR
|
The first element of the array contains a read-write flag that indicates the type of operation that caused the access violation. If this value is zero, the thread attempted to read the inaccessible data. If this value is 1, the thread attempted to write to an inaccessible address.
If this value is 8, the thread caused a user-mode data execution prevention (DEP) violation.
The second array element specifies the virtual address of the inaccessible data.
The third array element specifies the underlying NTSTATUS code that resulted in the exception.
|
To enable a debugger to debug a target that is running on a different architecture (32-bit versus 64-bit), use one of the explicit forms of this structure.
typedef struct _EXCEPTION_RECORD32 {
DWORD ExceptionCode;
DWORD ExceptionFlags;
DWORD ExceptionRecord;
DWORD ExceptionAddress;
DWORD NumberParameters;
DWORD ExceptionInformation[EXCEPTION_MAXIMUM_PARAMETERS];
} EXCEPTION_RECORD32, *PEXCEPTION_RECORD32;
typedef struct _EXCEPTION_RECORD64 {
DWORD ExceptionCode;
DWORD ExceptionFlags;
DWORD64 ExceptionRecord;
DWORD64 ExceptionAddress;
DWORD NumberParameters;
DWORD __unusedAlignment;
DWORD64 ExceptionInformation[EXCEPTION_MAXIMUM_PARAMETERS];
} EXCEPTION_RECORD64, *PEXCEPTION_RECORD64;
Requirements
Requirement |
Value |
Minimum supported client |
Windows XP [desktop apps | UWP apps] |
Minimum supported server |
Windows Server 2003 [desktop apps | UWP apps] |
Header |
winnt.h (include Windows.h) |
See also
EXCEPTION_DEBUG_INFO
EXCEPTION_POINTERS
GetExceptionInformation
RaiseException
UnhandledExceptionFilter