http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55917
--- Comment #5 from Tobias Ringström <tobias at ringis dot se> 2013-01-09 14:06:08 UTC --- Yes, I thought two reports were in order, as they are only vaguely related. To me, this one is the most important problem. I struggle to understand how I can be the first to have this problem. Surely it must be an enormous problem if you use std::thread? I'm working on a somewhat large multi-threaded program, and if there's an exception anywhere, e.g. a failed range-check in a container, it's *completely impossible* to find the problem in a debugger. We've now switched to boost::thread instead because it does not have this problem. I must say that I'm very surprised that you call it an enhancement, and that you consider closing it as WONTFIX, seeing how the current behavior is so mindbogglingly unfriendly. There is a reason why GCC does not unwind the stack for non-threaded unhandled exceptions. Perhaps std::thread is not widely used yet, or I'm the only one with buggy code?
