Hi all,

If any function called by a BOOST_GLOBAL_FIXTURE makes a BOOST_XXXX macro call my test case is terminated with a SIGSEGV. I assume that this is because some part of the boost test framework has not been initialised as the point where by call is made.

Is this a known problem or is this intentional behaviour?

If this is intentional what should I do instead of calling BOOST_MESSAGE / BOOST_FAIL / BOOST_CHECK (for now I have replaced the last 2 with assert but this is not ideal...).

Regards

Mark