Обсуждение статьи тематического каталога: Поиск утечек памяти при помощи GPT, Valgrind, Exmap, dmalloc и Electric Fence (memory performance gpt debug)

Ссылка на текст статьи: http://www.opennet.dev/base/dev/memory_leak_debug.txt.html

• Поиск утечек памяти при помощи GPT, Valgrind, Exmap, dmalloc и Electric Fence (memory performance gpt debug),pavlinux, 02:06 , 15-Ноя-10
• Поиск утечек памяти при помощи GPT, Valgrind, Exmap, dmalloc и Electric Fence (memory performance gpt debug),pavlinux, 03:31 , 15-Ноя-10
• а,ANDREI3, 05:14 , 07-Ноя-20

Куль!

Ага...  :)

==6504== Memcheck, a memory error detector
==6504== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==6504== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==6504== Command: src/fuck
==6504==

valgrind:  Fatal error at startup: a function redirection
valgrind:  which is mandatory for this platform-tool combination
valgrind:  cannot be set up.  Details of the redirection are:
valgrind:  
valgrind:  A must-be-redirected function
valgrind:  whose name matches the pattern:      strlen
valgrind:  in an object with soname matching:   ld-linux-x86-64.so.2
valgrind:  was not found whilst processing
valgrind:  symbols from the object with soname: ld-linux-x86-64.so.2
valgrind:  
valgrind:  Possible fixes: (1, short term): install glibc's debuginfo
valgrind:  package on this machine.  (2, longer term): ask the packagers
valgrind:  for your Linux distribution to please in future ship a non-
valgrind:  stripped ld.so (or whatever the dynamic linker .so is called)
valgrind:  that exports the above-named function using the standard
valgrind:  calling conventions for this platform.
valgrind:  
valgrind:  Cannot continue -- exiting now.  Sorry.

Гуль