-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
windows: Bug in boost::condition_variable on Windows #130
Comments
I suspect that this was already fixed, isn't it? |
viboes
changed the title
Bug in boost::detail::basic_condition_variable on Windows
Bug in boost::condition_variable on Windows
Aug 24, 2017
You are right. Using the same name for the function was an source of errors. Thanks for catching this. |
viboes
added a commit
that referenced
this issue
Aug 24, 2017
viboes
added a commit
that referenced
this issue
Aug 24, 2017
viboes
changed the title
Bug in boost::condition_variable on Windows
windows: Bug in boost::condition_variable on Windows
Aug 24, 2017
viboes
added a commit
that referenced
this issue
Aug 28, 2017
viboes
added a commit
that referenced
this issue
Aug 28, 2017
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The bug was made in commit ace2b8f (see line 247)
Instead should be
entry.remove_waiter();
because of entry_manager has overloaded operator -> and the function is called on basic_cv_list_entry but not entry_manager itself. This results in synchronization issues.The text was updated successfully, but these errors were encountered: