From: David Abrahams (dave_at_[hidden])
Date: 2006-02-01 08:58:11
Thomas Witt <witt_at_[hidden]> writes:
> David Abrahams wrote:
>> "Robert Ramey" <ramey_at_[hidden]> 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
> 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
-- Dave Abrahams Boost Consulting www.boost-consulting.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk