Skip to content
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

fix issue #48. valgrind errors #49

Merged

Conversation

yuvalif
Copy link
Contributor

@yuvalif yuvalif commented Jan 20, 2019

when running example or tests under valgrind, "uninitialized" valgrind error is not seen

Signed-off-by: Yuval Lifshitz yuvalif@yahoo.com

Signed-off-by: Yuval Lifshitz <yuvalif@yahoo.com>
Copy link
Collaborator

@timblechmann timblechmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is kind of a false positive of valgrind: the ABA counter doesn't need to be initialised, we only need to make sure that it increments.
but it won't do much harm to initialise it

include/boost/lockfree/queue.hpp Outdated Show resolved Hide resolved
Signed-off-by: Yuval Lifshitz <yuvalif@yahoo.com>
@yuvalif
Copy link
Contributor Author

yuvalif commented Feb 20, 2019

@timblechmann any other fixes needed in the PR?

@timblechmann timblechmann merged commit 7e23dac into boostorg:develop Feb 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants