Re: Handle C++ exception and structured exception together
"George" <George@discussions.microsoft.com> wrote in message
news:E81EF2A3-1D40-46EA-A22A-97FC95FF56A7@microsoft.com
1. set_se_translator only works for /EHa mode;
Basically correct.
2. in /EHsc mode, when there are programming errors, like
dereferencing a NULL pointer, structured exception will not occur and
program will report error and let end user select to debug;
This is just nonsense. Which part of "/EHsc doesn't magically suppress
structured exceptions. They still happen" do you have difficulty
understanding? What's the point of asking questions if you don't read,
or refuse to understand, the answers? Why waste yours and everybody
else's time?
This error dialog is shown when a structured exception occurs in the
program and unwinds all the way to the OS startup code (the code that
actually calls your WinMain or your thread proc) uncaught and unhandled.
The OS handles all structured exceptions at the very top of the stack,
and shows this error dialog.
Since this is the OS behavior, compiler switches have no effect on it.
See also SetUnhandledExceptionFilter.
3. /EHa mode is more accurately a mixed mode of structured exception
and C++ exception, not structured exception only
I'm curious how in your study you managed to come to contradictory
conclusions. If, as you claim, no structured exceptions at all occur in
/EHsc mode, how can /EHa mode be _more_ accurate in handling them?
Reminds me of a mad tea-party:
http://books.google.com/books?id=zEDDSh8nHwQC&pg=PA61&sig=g4ayK4b_PO7FWBVJ-ovC_O6jvxk#PPA66,M1
Last line on page 66 and on.
--
With best wishes,
Igor Tandetnik
With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925