Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
MSDN describes UnhandledExceptionFilter as follows: “An application-defined function that passes unhandled exceptions to the debugger, if the process is being debugged.”
But this function is clearly supplied by the OS, in kernel32.dll according to that same page.
So why do they call it an application-defined function?
Yes, very awkward language. It is a prototype definition of a function. Which you can use with the __except keyword or as an argument to SetUnhandledExceptionFilter(). Either would make yours an ‘application defined function’.
There’s default handling if you do neither, the debugger automatically stops at an unhandled exception. Which I suppose is what they meant with “that passes exceptions to the debugger”. The SDK docs for SEH deserve an all-around failing grade.