I find the catch(...) in thread_proxy to be a real nuisance. The only
can do to prevent threads from silently slipping away is to put a
inside my thread procedure, but when this is hit I have no idea what the
exception is or where it was thrown. I could configure the debugger
break whenever an exception is thrown, but then I have to wade through
exceptions in order to find the real error.
There was a discussion on this subject about eight months ago where the
consensus seemed to be get rid of the catch(...)--any progress on this
then? I notice the catch(...) is still present in CVS, which isn't
As a refresher, this approach won't help...
exception_filter(); // ... because I don't have a stack trace here.