SPS_EXCEPTION (Windows Embedded CE 6.0)
1/6/2010
This structure contains information for the exception that was generated.
Syntax
typedef struct _SPS_EXCEPTION {
LPFUNCTION_TABLE_ENTRY lpFTE;
DWORD dwExceptionCode;
EXCEPTION_POINTERS* lpExceptionPointers;
DWORD dwExceptionFilter;
} SPS_EXCEPTION, *LPSPS_EXCEPTION;
Members
- lpFTE
Pointer to the FUNCTION_TABLE_ENTRY structure within your test module's function table for the test case that raised the exception. This member is NULL if the exception occurred in your ShellProc function.
- dwExceptionCode
Specifies the type of exception that occurred. This is the same value that GetExceptionCode returns.
- lpExceptionPointers
Pointer to an EXCEPTION_POINTERS structure that contains the exception context and one or more exception records. This is the same value that GetExceptionInformation returns. You may alter the values within the exception context if you want to retry the exception with an altered context.
dwExceptionFilter
Specifies the exception filter value that will be used to resolve the exception.The following table shows all valid values.
Value Description EXCEPTION_EXECUTE_HANDLER
This is the default value, which causes the exception to be handled as gracefully as possible, and resumes execution with the next test in the script.
EXCEPTION_CONTINUE_SEARCH
Changing dwExceptionFilter to this value passes the exception to the debugger, if one is present. If no debugger is present, Tux and all loaded DLLs will terminate immediately and the exception will not be handled.
EXCEPTION_CONTINUE_EXECUTION
Changing dwExceptionFilter to this value causes the system to retry the exception again. Unless you alter the exception context to fix the exception, you will most likely return to the SPM_EXCEPTION message handler. Use caution when using this value, so as not to get caught in an infinite exception-handling loop.
Requirements
| Header | tux.h |
| Windows Embedded CE | Windows CE 3.0 and later |