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
A note Regarding double try-catch.
They seem to be useless in our case because we're using C++11
In C++11 another exception cannot be thrown if there's already one in-flight, it will trigger std::terminate immediately. What's to do:
Implement custom std::terminate handler to catch and log such issues (at least we will be aware that smth went wrong) -- done
Consider adding to the code standard using noexcept(false) in destructors.
Make all logging routines and mactors excepton-safe.
Make sure all this stuff passes Covetity
Refactor CATCH_* macros
The text was updated successfully, but these errors were encountered:
Set up Coverity and incorporate it in CI scheme.
A note Regarding double try-catch.
They seem to be useless in our case because we're using C++11
In C++11 another exception cannot be thrown if there's already one in-flight, it will trigger
std::terminate
immediately. What's to do:std::terminate
handler to catch and log such issues (at least we will be aware that smth went wrong) -- donenoexcept(false)
in destructors.The text was updated successfully, but these errors were encountered: