Question

这个valgrind输出让我感到困惑，因为它似乎没有引用我的代码，并且我已经使用STL编写了多个程序，尽管没有HEAP SUMMARY错误：

$ valgrind -v --leak-check=full --track-origins=yes ./hellostl

...

==7989== Conditional jump or move depends on uninitialised value(s)
==7989==    at 0x4017AA6: index (in /lib64/ld-2.17.so)
==7989==    by 0x4007A12: expand_dynamic_string_token (in /lib64/ld-2.17.so)
==7989==    by 0x4008304: _dl_map_object (in /lib64/ld-2.17.so)
==7989==    by 0x400181D: map_doit (in /lib64/ld-2.17.so)
==7989==    by 0x400E985: _dl_catch_error (in /lib64/ld-2.17.so)
==7989==    by 0x40010EF: do_preload (in /lib64/ld-2.17.so)
==7989==    by 0x40039D7: dl_main (in /lib64/ld-2.17.so)
==7989==    by 0x40152B7: _dl_sysdep_start (in /lib64/ld-2.17.so)
==7989==    by 0x4004E94: _dl_start (in /lib64/ld-2.17.so)
==7989==    by 0x4001637: ??? (in /lib64/ld-2.17.so)
==7989==  Uninitialised value was created by a stack allocation
==7989==    at 0x4003961: dl_main (in /lib64/ld-2.17.so)
==7989==
==7989== Conditional jump or move depends on uninitialised value(s)
==7989==    at 0x4017AAB: index (in /lib64/ld-2.17.so)
==7989==    by 0x4007A12: expand_dynamic_string_token (in /lib64/ld-2.17.so)
==7989==    by 0x4008304: _dl_map_object (in /lib64/ld-2.17.so)
==7989==    by 0x400181D: map_doit (in /lib64/ld-2.17.so)
==7989==    by 0x400E985: _dl_catch_error (in /lib64/ld-2.17.so)
==7989==    by 0x40010EF: do_preload (in /lib64/ld-2.17.so)
==7989==    by 0x40039D7: dl_main (in /lib64/ld-2.17.so)
==7989==    by 0x40152B7: _dl_sysdep_start (in /lib64/ld-2.17.so)
==7989==    by 0x4004E94: _dl_start (in /lib64/ld-2.17.so)
==7989==    by 0x4001637: ??? (in /lib64/ld-2.17.so)
==7989==  Uninitialised value was created by a stack allocation
==7989==    at 0x4003961: dl_main (in /lib64/ld-2.17.so)

我是否有可能使用过时的版本（例如编译器，valgrind ......）？

编辑：触发错误的简单代码：

#include <vector>
#include <iostream>
using namespace std;

int main ()
{
    vector<int> foo;
    for (int i = 0; i < 50; ++i)
        foo.push_back( i );

    for (auto it = foo.begin();
        it != foo.end();
        ++it)
    {
        cout << *it << endl;
    }
}

Answer 1

动态链接库因引起Valgrind警告而臭名昭着。你观察到的那个实际上是一个非常普遍的。您无法修复此警告，但如果它让您烦恼，则可以添加抑制规则。

进一步说明，这里发生的事情是在程序运行之前，C ++标准库是动态链接的。如果您使用ldd检查二进制文件，则应该看到如下所示的行：

    libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fa0e2f72000)

如果您要静态链接此库，您的程序将在没有动态链接的情况下运行，警告将消失。

Valgrind'未初始化的值'依赖不引用我的代码

1 个答案: