Re: [boost] [test] Re: Conflicts when building libraries at root

Subject: Re: [boost] [test] Re: Conflicts when building libraries at root
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2015-03-09 18:28:45

On 03/09/2015 03:25 PM, Gavin Lambert wrote:
> On 10/03/2015 10:34, Vladimir Prus wrote:
>> On 03/09/2015 02:24 PM, Andrey Semashev wrote:
>>> On Monday 09 March 2015 23:15:16 Peter Dimov wrote:
>>>> Jürgen Hunold wrote:
>>>>> Am Montag, 9. März 2015, 13:14:48 schrieb Vladimir Prus:
>>>>>>   This [asynch-exceptions on] does not seem like a feature we can
>>>>>> globally set?
>>>>>
>>>>> Perhaps we can, but I'm not an expert in vc exception handling...
>>>>
>>>> No, I very much would not like everything to be built with
>>>> asynch-exceptions on.
>>>
>>> +1, SEH should be done explicitly where required and not mixed up with
>>> C++ exceptions.
>>
>> So why is Boost.Test enabling those? Are there any particular files in
>> Boost.Test that need it?
>
> I haven't looked at the code, but I suspect it is so that it can intercept such faults (eg. null pointer dereferences) and translate them
> into test failures.
>
> _set_se_translator can be used to automatically convert SEH exceptions into a specific C++ exception (which is better than using
> catch(...)), but /EHa must be enabled on the code where the exception is thrown in order to get an accurate location.

Thanks for explanation! So if that's about code where the exception is *thrown*, it would seem Boost.Test should not need
to set this option on itself? It would be up to users to either enable that mode if they want Boost.Test to report SEH exceptions,
or not do that.

Thanks,

-- 
Vladimir Prus
CodeSourcery / Mentor Embedded
http://vladimirprus.com