structured-exception

I have a function in which I call getaddrinfo() to get an sockaddr* which targets memory is allocated by the system. As many may know, you need to call freeaddrinfo() to free the memory allocated by getaddrinfo(). Now, in my function, there are a few places, where I may throw an exception, because some function failed. My first solution was to incorporate the freeaddrinfo() into every if-block. But that did look ugly for me, because I would have had to call it anyways before my function returns, so I came up with SEH`s try-finally... But the problem I encountered is, that it is not allowed to

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 setup set_terminate() and set_unexpected() . To get the Stack Overflow, I must run in release mode, under heavy load, for several days. Running under a debugger is not an option as the application can't perform fast enough to achieve the runtime necessary to see the

Usually an access violation terminates the program and I cannot catch a Win32 exception using try and catch . Is there a way I can keep my program running, even in case of an access violation? Preferably I would like to handle the exception and show to the user an access violation occurred. EDIT: I want my program to be really robust, even against programming errors. The thing I really want to avoid is a program termination even at the cost of some corrupted state. In Windows, this is called Structured Exception Handling (SEH). For details, see here: http://msdn.microsoft.com/en-us/library

What important points about Structured Exceptions should every C++ developer know? They are the Win32 equivalent to Unix signals, and let you catch CPU exceptions such as access violation, illegal instruction, divide by zero. With the right compiler options (/EHa for Visual C++), C++ exceptions use the same mechanism as stack unwinding works properly for both C++ (user) exceptions and SEH (OS) exceptions. Unlike C++ exceptions, SEH are not typed but all share the same data structure which has an exception code (the cause) and additional information on what code faulted and what the CPU