On 06/25/2011 11:16 AM, rafael ferraz wrote: > ==2486== Conditional jump or move depends on uninitialised value(s) > ==2486== at 0x338C016BD6: index (in /lib64/ld-2.14.so) > ==2486== by 0x338C007547: expand_dynamic_string_token (in > /lib64/ld-2.14.so)
> This could be classified as a bug? I need to report it? Yes, it is a bug. Memcheck failed to intercept this call to 'index'. The interception is necessary because the actual code for 'index' is too complicated for memcheck to check easily, which causes many false-positive error reports (such as the one above.) When the interception works, then memcheck re-directs the execution to equivalent code which is easier to check with no false-positive reports of errors. See http://valgrind.org/support/bug_reports.html for reporting the bug. Search first to see if somebody else already has reported this problem. If not, then go ahead and enter a bug report. You'll need to identify which Linux distribution and release, the version of the C library runtime system, and the version of valgrind that you are using. -- ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
