Re: [boost] [thread] thread_proxy's catch(...) destroys my stack info for unhandled exceptions

On Friday 26 December 2008 20:49:55 Roberto Gimenez wrote:

When some unhandled exception is thrown inside my function, it would be good that is isn't actually handled, so I could collect the stack info from the core-dump.

There was a thread "[Thread] Win32 exception handling", starting 2008-11-25, which had exactly this behaviour as reason. Before rehashing every argument over, I would suggest reading that.

So why is:

catch(...) { std::terminate(); }

there? It looks unnecesary.

I think it is necessary for environments where std::terminate is not called automatically, but that is no excuse for doing it unconditionally. Uli