You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
vladlosev
on 13 Nov 2010 at 3:07The text was updated successfully, but these errors were encountered: