Printable View
is there some clearance sell on SExceptions today??? just in time for christmas??? This must make my 6th comment on it today...Quote:
Originally posted by CornedBee
Aside from fully agreeing with the previous posters, you can catch Windows SEH exceptions with
catch(...)
but you don't know what hit you.
install a set_se_translator(...) re-throw, after a stackwalk(...) if you like...your catch(...) becomes catch(unsigned int foo)
And you don't know what state your process or thread is in. Did the thread have a stack overflow? Are you sure you can recover? Was there a privileged instruction? Did the thread forget to release a mutex in the stack-unwinding? etc...Quote:
Originally posted by CornedBee
Aside from fully agreeing with the previous posters, you can catch Windows SEH exceptions with
catch(...)
but you don't know what hit you.
All of which brings us back to: fix the underlying problem. ;)
Yep. Oh, and stack overflows cannot be caught that way.
Incorrect.Quote:
Originally posted by CornedBee
Yep. Oh, and stack overflows cannot be caught that way.
An exception 0xc00000fd sure can be caught by "catch( ... )" or by using structured exception handling via set_se_translator...
Right. Hmm, I was sure that I remembered something written about stack overflows immediatly and irrecoverably terminating the application.
Well... if you don't catch it... :)Quote:
Originally posted by CornedBee
Right. Hmm, I was sure that I remembered something written about stack overflows immediatly and irrecoverably terminating the application.
Anyone catching an "exception" that results from undefined behaviour including platform-specific failures (such as a stack overflow), really needs to hit the (C++) books again.Quote:
Originally posted by vicodin451
Incorrect.
An exception 0xc00000fd sure can be caught by "catch( ... )" or by using structured exception handling via set_se_translator...
The "void main()" is a typically a giveaway that though this is the non-VC++ forum, the OP is using VC++. The talk of structured exceptions is of course Windows-specific.Quote:
Originally posted by Sef
Anyone catching an "exception" that results from undefined behaviour including platform-specific failures (such as a stack overflow), really needs to hit the (C++) books again.
IIRC, Richter details an example of catching a stack overflow and recovering from it in "Programming Applications for Microsoft Windows".
At any rate, if you will follow this thread, you will see that it was not recommended that the OP do anything along the lines of catching any sort of "exception" caused by "undefined behavior". The OP was urged to correct the problem rather than hide its effects.