> I also can't believe, that I am expected to generate a big list of > suppression files just to make valgrind not complain about glibc - even > when running /bin/echo.
I get no complaints when running memcheck [with default suppressions, which are installed automatically] on Fedora 14 (beta) or Fedora 13 on x86_64. What are you running? > $ valgrind /bin/echo > ==18645== Memcheck, a memory error detector > ==18645== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al. > ==18645== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info > ==18645== Command: /bin/echo > ==18645== > ==18645== Conditional jump or move depends on uninitialised value(s) > ==18645== at 0x40166D6: index (strchr.S:56) Which distribution of Linux are you running? There was a period of time when SuSE built its ld-linux.so.2 without the information that valgrind needs to intercept and replace the out-of-line, yet optimized, strchr/ strrchr/index/strlen/etc with memcheck's own versions that are more friendly towards error checking. To diagnose: readelf --symbols /lib*/ld-linux*.so.* | grep index If there is no line similar to this one [for x86-64]: 356: 0000003a9fc16ca0 124 FUNC LOCAL DEFAULT 11 index then you suffer from this problem. If so, then send a polite complaint to your distro, asking them to work better with valgrind by not applying "strip" when building ld-linux. -- ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Valgrind-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/valgrind-users
