|
From: John R. <jr...@bi...> - 2011-05-12 14:58:03
|
> Hi, in the packaging readme[0] for valgrind it's stated that it's a bad > idea to strip what's in /usr/lib/valgrind/ ... > FWIW this is a matter of 227Mb large /usr/lib/valgrind versus 71Mb without > debug. Which machine architecture and compiler? There's a difference between stripped (applying /usr/bin/strip, /usr/bin/objcopy, flags such as -s -S to /usr/bin/ld, etc.) and non-debug (no -g in CFLAGS). Only developers of valgrind need debug symbols (-g) inside valgrind itself. After installing a recent Fedora 15 .rpm for valgrind-3.6.1: ----- $ ls -l /usr/bin/valgrind /usr/lib64/valgrind/memcheck-amd64-linux -rwxr-xr-x. 1 root root 43260 May 3 02:49 /usr/bin/valgrind -rwxr-xr-x. 1 root root 13742515 May 3 02:49 /usr/lib64/valgrind/memcheck-amd64-linux $ file /usr/bin/valgrind /usr/lib64/valgrind/memcheck-amd64-linux /usr/bin/valgrind: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.32, not stripped /usr/lib64/valgrind/memcheck-amd64-linux: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), statically linked, not stripped ----- > Secondly, valgrinds installs a few archives namely: > /usr/lib/valgrind/libcoregrind-amd64-linux.a > /usr/lib/valgrind/libcoregrind-x86-linux.a > /usr/lib/valgrind/libreplacemalloc_toolpreload-amd64-linux.a > /usr/lib/valgrind/libreplacemalloc_toolpreload-x86-linux.a > /usr/lib/valgrind/libvex-amd64-linux.a > /usr/lib/valgrind/libvex-x86-linux.a These are needed only for development of valgrind tools. They are not needed for ordinary invocation of valgrind tools. -- |