无法理解valgrind的输出

时间:2012-07-06 08:19:17

标签: valgrind memcheck

无法理解.eh_frame部分映射

     ==4780== Use of uninitialised value of size 4
     ==4780==    at 0x4011D18: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x401628F: ???
     ==4780==    by 0x4006227: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x40065EF: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x4009E33: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x400B437: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x400A29F: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x4002ECB: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x400DF03: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x4001BD3: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x400215F: ??? (in /lib/ld-2.3.2.so)
     ==4780==    by 0x400EF2B: ??? (in /lib/ld-2.3.2.so)
    ==4780==
     ==4780== Use of uninitialised value of size 4
     ==4780==    at 0x4011D28: ??? (in /lib/ld-2.3.2.so)
     ==4780==
     --4780-- WARNING: Serious error when reading debug info

1 个答案:

答案 0 :(得分:1)

您显示的输出表示/lib/ld-linux.so.2已被剥离。

通常默认Valgrind抑制会抑制此输出(因为无论如何你都无法对这些错误做任何事情)。安装glibc-debug-2.3.2 *包可能会有所帮助。

ld-linux.so.2被剥离时,最近的Valgrind版本拒绝运行。但是,由于您使用的是古代 glibc-2.3.2(2003年3月发布),您可能也使用了古老版本的Valgrind,但没有。