id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
11278	--detect_memory_leaks useless without --catch_system_errors=n	willi@…	Raffi Enficiaud	"When using the unit test framework's runtime option `--detect_memory_leaks=N` (described in http://www.boost.org/doc/libs/1_58_0/libs/test/doc/html/utf/user-guide/runtime-config/reference.html) the resulting breakpoint is caught by the framework unless `--catch_system_errors` is set to `n`. This causes the debug break to not happen until halfway through the reporting of this fatal ""breakpoint encountered"" error, rendering the call stack useless.

This should at least be mentioned in the documentation; maybe `detect_memory_leaks` should imply `catch_system_errors=n`.

I'm on Windows 7x64 in a 32 bit debug build using MSVC14RC and the multithreaded static boost.test library."	Bugs	closed	Boost 1.63.0	test	Boost 1.58.0	Problem	obsolete