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
Describe the problem
If an exception occurs during the automatic unlocking in the destructor of std::lock_guard,it seems to cause the program to terminate. Here is an example, I manually shutdown the Redis before the deconstruction of std::lock_guard:
I manually shutdown the Redis before the deconstruction of std::lock_guard
Sorry, I missed this. Yes, this is a problem. Looks like that unlock should not throw. However, in this case, application which calls unlock directly, cannot tell if unlock successes or not.
Thanks for reporting it! I'll rethink it, and fix it.
Describe the problem
If an exception occurs during the automatic unlocking in the destructor of
std::lock_guard
,it seems to cause the program to terminate. Here is an example, I manually shutdown the Redis before the deconstruction ofstd::lock_guard
:I think the reason is that the exception is re-thrown in the destructor. Here is the source code of redispp:
Environment:
The text was updated successfully, but these errors were encountered: