Hi Thorsten, I normally place soft breakpoint in the code that announces the test failure and walk the call stack. 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. See: http://msdn2.microsoft.com/en-us/library/ms680345.aspx for IsDebuggerPresent() I hope this helps, 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 14:56 To: boost@lists.boost.org Subject: [boost] [test] integration with debugger Hi all, Has anybody successfully integrated the debugger with boost.test/unit_test with visual studio 7/8? I'm a bit annoyed that I don't break into the debugger, when an assertion triggers. Thanks in advance -Thorsten _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost