valgrind reports many "Conditional jump or move depends on uninitialised value(s)" about nmos-cpp HOT 3 CLOSED

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 web::json::details::_String::has_escape_chars, I have examined the call stacks in the valgrind log, and looked at the code, and cannot find a reason for these. I can't say for certain, but I suspect a false positive. (In fact as you said, these could also ultimately be down to the same Boost.UUID issue, as the nmos::experimental::details::json_from_message function uses a stringised UUID.)

Are there any others?

from nmos-cpp.

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.

from nmos-cpp.

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 letting me know!

from nmos-cpp.