-
Notifications
You must be signed in to change notification settings - Fork 80
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
valgrind reports many "Conditional jump or move depends on uninitialised value(s)" #9
Comments
Thank you for the report! The reported issues with the Boost.Random and Boost.UUID libraries seem to be expected - these intentionally depend on uninitialized data. However, I did find e.g. https://svn.boost.org/trac10/ticket/9407, which suggests that a patch was applied in Boost 1.59.0 that may resolve these. If you're using an older version of Boost, it could be worth trying a more recent one. As for the issues ultimately reported within C++ REST SDK's Are there any others? |
We're running boost 1.58, of course! I'll have to see if I can convince the PTB to upgrade. In any event, I was able to make a private build using boost 1.65 and valgrind reports no problems in nmos-cpp-node with the latest master branch. Thanks for your help. |
Thanks for letting me know! |
Remove redundant parameters.
Hi, again,
I'm running valgrind in an attempt to find my own bugs but am seeing a lot of errors with uninitialized values in commit 91cb17d. I suspect a lot of the messages are a consequence of the first one -- the random number generator is seeded with something uninitialized, which means that all the uuids are uninitialzed, which means everything that refers to them are.
The text was updated successfully, but these errors were encountered: