GNOME Bugzilla – Bug 780406
Valgrind warns about uninitialized data
Last modified: 2017-03-23 18:04:20 UTC
I've met those message when running python/gi inside valgrind. I do think this is just noise, but still, have wrote a patch to silence it (patch coming). ==30861== Conditional jump or move depends on uninitialised value(s) ==30861== at 0x4ED387A: PyLong_FromLong (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x16D62760: _pygi_argument_to_object (pygi-argument.c:1424) ==30861== by 0x16D5BEC4: _wrap_g_constant_info_get_value (pygi-info.c:1724) ==30861== by 0x4F5EB3C: PyEval_EvalFrameEx (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4F605E2: ??? (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4F606C2: PyEval_EvalCodeEx (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4ECABF7: ??? (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4E9FED6: PyObject_Call (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4EB6933: ??? (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4E9FED6: PyObject_Call (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4EA0AE1: PyObject_CallFunctionObjArgs (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4EF791E: ??? (in /usr/lib64/libpython3.5m.so.1.0)
Created attachment 348510 [details] [review] pygi-info: Initialize GIArgument structure to 0 This is purely cosmetic, at least I could not find any impact, but it removes valgrind noise that this is being used uninitialized. An example backtrace in valgrind looked like: ==30861== Conditional jump or move depends on uninitialised value(s) ==30861== at 0x4ED387A: PyLong_FromLong (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x16D62760: _pygi_argument_to_object (pygi-argument.c:1424) ==30861== by 0x16D5BEC4: _wrap_g_constant_info_get_value (pygi-info.c:1724) ==30861== by 0x4F5EB3C: PyEval_EvalFrameEx (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4F605E2: ??? (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4F606C2: PyEval_EvalCodeEx (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4ECABF7: ??? (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4E9FED6: PyObject_Call (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4EB6933: ??? (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4E9FED6: PyObject_Call (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4EA0AE1: PyObject_CallFunctionObjArgs (in /usr/lib64/libpython3.5m.so.1.0) ==30861== by 0x4EF791E: ??? (in /usr/lib64/libpython3.5m.so.1.0)
Thanks :) See https://git.gnome.org/browse/pygobject/commit/?id=399939b55860211e0ab64bdfbfada2c86be8bf64
I've pushed it to the 3-24 stable branch as well now *** This bug has been marked as a duplicate of bug 772949 ***
Thanks to you.