id	summary	reporter	owner	description	type	status	milestone	component	version	severity	resolution	keywords	cc
2349	execution monitor and terminate()	Norbert Buchmuller <norbi@…>	Gennadiy Rozental	"In versions 1.35.0 and 1.36.0 the execution monitor does not detect if {{{terminate()}}} is called. In the current trunk (r48903) it does, but still does not have any test cases for this condition (so I think it was fixed without knowing the problem). I think a test case would be useful to detect regressions.

I noticed this problem with GCC 3.4.6 and GCC 4.1.2 on i486-linux-gnu. These compilers always call {{{terminate()}}} from {{{unexpected()}}} (ie. they call {{{terminate()}}} even if {{{std::bad_exception}}} is in the throw-list), and {{{terminate()}}} calls {{{abort()}}}."	Bugs	closed	Boost 1.37.0	test	Boost 1.36.0	Problem	worksforme