Re: Mixing /EHs and /EHa (structured exceptions)
"Kenneth Porter" <shiva.blacklist@sewingwitch.com> wrote in message
news:Xns99A8753A821DEshivawellcom@207.46.248.16...
"Ben Voigt [C++ MVP]" <rbv@nospam.nospam> wrote in
news:O0KL1uH9HHA.396@TK2MSFTNGP06.phx.gbl:
Nonetheless, it is perfectly appropriate to add an SEH handler to a
program mostly compiled with /EHs. The OP did after all describe it
as a "crash handler". The undetermined state of the program will be
no worse than if the exception was not caught at all, and certainly
some useful information can be dumped such as a stack trace or
minidump.
Thanks. The code in question is in a cross-platform library and it's
trying
to provide the same service under Windows that Unix provides via "core"
files as a basic part of the OS. With Windows, an application must
explicitly save a minidump that can later be loaded into a debugger for
post-mortem analysis. With Linux and other Unix-alikes, the application
needs no special code to do this.
Is there some way I can request /EHa for just this one module using a
pragma? Or do I need to do it in the file's compiler settings as part of
the project?
You can use __try/__except in a program compiled with /EHs, according to the
doc page for __try. It will catch any and all exceptions.
You need __except so you can call the GetExceptionInformation function, the
doc page for MiniDumpWriteDump says:
MiniDumpWriteDump may not produce a valid stack trace for the calling
thread. To work around this problem, you must capture the state of the
calling thread before calling MiniDumpWriteDump and use it as the
ExceptionParam parameter. One way to do this is to force an exception inside
a __try/__except block and use the EXCEPTION_POINTERS information provided
by GetExceptionInformation. Alternatively, you can call the function from a
new worker thread and filter this worker thread from the dump.