From: Neil Groves (neil_at_[hidden])
Date: 2007-12-09 13:43:53
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.
From: boost-bounces_at_[hidden] [mailto:boost-bounces_at_[hidden]]
On Behalf Of Thorsten Ottosen
Sent: 09 December 2007 16:40
Subject: Re: [boost] [test] integration with debugger
Neil Groves skrev:
> Hi Thorsten,
> I normally place soft breakpoint in the code that announces the test
> 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
> 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.
Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk