-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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: Conditional jump or move depends on uninitialised value(s) #3433
Comments
Interesting, we need to check these. Thank you for the report |
I tested the latest development version on ubuntu 16.04. I found some memory leaks ("blocks are indirectly lost", "blocks are still reachable", etc.) but no "Conditional jump or move depends on uninitialised value(s)". errors. Tested with both v4l and rsusb backends. |
I have at least a similar issue. Here is the valgrind (memcheck) backtrace collected with --track-origins=yes
Interestingly this issue only shows up in valgrind within a bigger codebase, so far I have not managed to recreate it with a minimal example. After a little bit of investigation, my guess was that the problem lies here in the frame additional_data constructor
std::copy only initializes part of the buffer metadata_blob. In use this then later shows up in valgrind. In sensors.hpp as a stack allocation:
After adding std::array::fill to the constructor
valgrind is completely satisfied. However the call still fails, with the same error:
It seems to work now, but i'm not sure if this actually fixed the underlying issue. Version info:
|
Issue Description
Maybe it is just some false positives but I get
Conditional jump or move depends on uninitialised value(s)
errors with the following code and latest librealsense:Log:
The text was updated successfully, but these errors were encountered: