Thomas Witt <witt@acm.org> writes:
David Abrahams wrote:
"Robert Ramey" <ramey@rrsd.com> writes:
I practice I fire up my debugger on any failed test and set my VC debugger to trap on any exception - this works great for me.
IIRC, you only get to see the program state after the program has unwound to the exception handler in the test library. That's too late.
FWIW VC supports breaking on throw. I.e. you'll see the program state before any stack unwinding happened. IIRC this can be controllled on a exception type basis.
Yes, that works great if you happen to be running under the debugger. Sometimes a test crash is the result of difficult-to-reproduce conditions, and if you lose your opportunity to JIT it, the game is up. -- Dave Abrahams Boost Consulting www.boost-consulting.com