Thorsten, I have been looking into this a little more and have discovered that there is also a --auto_start_dbg option. That might do exactly what you asked for. Neil Groves -----Original Message----- From: boost-bounces@lists.boost.org [mailto:boost-bounces@lists.boost.org] On Behalf Of Thorsten Ottosen Sent: 09 December 2007 16:40 To: boost@lists.boost.org Subject: Re: [boost] [test] integration with debugger Neil Groves skrev:
Hi Thorsten,
I normally place soft breakpoint in the code that announces the test failure and walk the call stack.
You are compiling directly with visual studio then? I'm usign bjam + slickedit as my enviroenment.
Alternatively you can use the IsDebuggerPresent() call combined with DebugBreak as a Windows only modification to the assertions. This only causes a debug break if a developer has attached a local debugger. The automated unit test execution is unaffected.
I would prefer if the the unit-test itself could be debugged. The unite-test makes no sense if there is a serious assertion triggering somewhere.
I'm a bit annoyed that I don't break into the debugger, when an assertion triggers.
When I write a normal program, it crashes and allows me to debug it...with boost.test, the behavior has been modified somehow. -Thorsten _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost