11

当我使用 valgrind 帮助调试我正在开发的应用程序时，我注意到大量噪音似乎在抱怨标准库。作为测试，我这样做了；

echo 'int main() {return 0;}' | gcc -x c -o test -

然后我这样做了；

valgrind ./test

==1096== Use of uninitialised value of size 8
==1096==    at 0x400A202: _dl_new_object (in /lib64/ld-2.10.1.so)
==1096==    by 0x400607F: _dl_map_object_from_fd (in /lib64/ld-2.10.1.so)
==1096==    by 0x4007A2C: _dl_map_object (in /lib64/ld-2.10.1.so)
==1096==    by 0x400199A: map_doit (in /lib64/ld-2.10.1.so)
==1096==    by 0x400D495: _dl_catch_error (in /lib64/ld-2.10.1.so)
==1096==    by 0x400189E: do_preload (in /lib64/ld-2.10.1.so)
==1096==    by 0x4003CCD: dl_main (in /lib64/ld-2.10.1.so)
==1096==    by 0x401404B: _dl_sysdep_start (in /lib64/ld-2.10.1.so)
==1096==    by 0x4001471: _dl_start (in /lib64/ld-2.10.1.so)
==1096==    by 0x4000BA7: (within /lib64/ld-2.10.1.so)
* large block of similar snipped *
==1096== Use of uninitialised value of size 8
==1096==    at 0x4F35FDD: (within /lib64/libc-2.10.1.so)
==1096==    by 0x4F35B11: (within /lib64/libc-2.10.1.so)
==1096==    by 0x4A1E61C: _vgnU_freeres (vg_preloaded.c:60)
==1096==    by 0x4E5F2E4: __run_exit_handlers (in /lib64/libc-2.10.1.so)
==1096==    by 0x4E5F354: exit (in /lib64/libc-2.10.1.so)
==1096==    by 0x4E48A2C: (below main) (in /lib64/libc-2.10.1.so)
==1096==
==1096== ERROR SUMMARY: 3819 errors from 298 contexts (suppressed: 876 from 4)
==1096== malloc/free: in use at exit: 0 bytes in 0 blocks.
==1096== malloc/free: 0 allocs, 0 frees, 0 bytes allocated.
==1096== For counts of detected errors, rerun with: -v
==1096== Use --track-origins=yes to see where uninitialised values come from
==1096== All heap blocks were freed -- no leaks are possible.

你可以在这里看到完整的结果：http: //pastebin.com/gcTN8xGp

我有两个问题；首先有没有办法抑制所有的噪音？

--show-below-main 默认设置为 no，但似乎没有 --show-after-main 等效项。

4

3 回答 3

12

您可以通过附加来抑制输出

{
   ld error suppression
   Memcheck:Cond
   fun:dl_main
   fun:_dl_sysdep_start
   fun:_dl_start
   obj:/lib64/ld-2.10.1.so
}

到/usr/lib/valgrind/default.supp（或定义您自己的抑制文件）。

至少对于 Debian 和 Arch Linux 开发人员来说，这似乎是一个已知的链接器/加载器错误；我不确定其余的，以及他们计划的行动方案。

于 2010-05-19T11:16:48.733 回答
5

升级到 Valgrind 3.5.0 或更高版本。除其他外，默认的 .supp 文件已更新。

于 2010-05-19T14:24:57.443 回答
4

我不时有这些症状，解决方案总是升级我的 valgrind 和 libc 包以同步。Debian 的可爱小精灵负责其余的工作。

于 2010-05-20T05:47:21.260 回答