Must not raise extra failures when Google Test has thrown GoogleTestFailureException.
GoogleCodeExporter opened this issue · comments
From the user's email:
http://groups.google.com/group/googlemock/browse_thread/thread/73036ce99f96d82a
When gMock reports a failure, it results in throwing GoogleTestFailureException
if it is being used with a third-party tets framework and the
--gtest_throw_on_failure flag. In this case, the remaining mocks will verify
their expectations from destructors during the stack unwinding. They will also
throw GoogleTestFailureException, resulting in the program calling terminate().
It looks like mocks should not verify their expectation during the stack
unwinding after GoogleTestFailureException is thrown. On Linux, this should be
done in a thread-safe manner.
Original issue reported on code.google.com by vladlosev on 13 Nov 2010 at 3:07