|
Boost : |
Subject: Re: [boost] [test] still broken in release
From: Gennadiy Rozental (rogeeff_at_[hidden])
Date: 2013-08-10 21:52:04
Bjorn Reese <breese <at>
mail1.stofanet.dk> writes:
>
> On 08/10/2013 07:11 PM, Gennadiy
Rozental wrote:
>
> Assuming that my foo() function fails,
how difficult is it going to be
> to single-step into it (without setting
breakpoints inside foo) from
> a BOOST_TEST(foo()) line? This is a very
common scenario for me.
New boost.test has support for this
through two macros:
BOOST_TEST_UNDER_DEBUGGER
If you define this test module will
compile in debugger friendly mode.
BOOST_TEST_DEBUGABLE
If you define this macro test module will
perform assertions as usual if you run the
test regularly and it will run in debugger
friendly mode of you run under debugger
(this only available on platforms where we
can detect presence of debugger). The
price you pay its extra compile time.
Gennadiy
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk