Background I have an application with a Poof-Crash[1]. I'm fairly certain it is due to a blown stack. The application is Multi-Threaded. I am compiling with "Enable C++ Exceptions: Yes With SEH Exceptions (/EHa)". I have written an SE Translator function and called _set_se_translator() with it. I have written functions for and set...
(Win32 platform c++) Using __try and __finally, how can I get the module name (And address) of the cause for an exception? I call GetExceptionInformation() but from that I am not sure where this information is. Given other resources online and in MSDN the Minidump handlers and other sample code seem to be able to get it, but I am not...
Could someone provide some example on implementing SEH in VB6? Everything I've seen so far is in C++ ...
What important points about Structured Exceptions should every C++ developer know? ...
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? ...
I am trying to understand the ways in which an unmanaged user-mode Windows process can "crash" (which is really too much of a catch-all term). Here are the ways I know of so far: Unhandled Structured Exception Default UnhandledExceptionFilter: postmortem debugger in pre-Vista; WerFault in Vista+ Custom UnhandledExceptionFilter: may d...