From 09c874db5300a1846a61cd675164d84974a4a8e0 Mon Sep 17 00:00:00 2001 From: Kamil Dudka Date: Wed, 16 May 2018 15:23:55 +0200 Subject: [PATCH] require glibc-debuginfo for valgrind-enabled build ... as suggested by valgrind itself: 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. The package you need valgrind: to install for fix (1) is called valgrind: valgrind: On Debian, Ubuntu: libc6-dbg valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo valgrind: valgrind: Note that if you are debugging a 32 bit process on a valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo valgrind: package (e.g. libc6-dbg:i386). valgrind: valgrind: Cannot continue -- exiting now. Sorry. --- curl.spec | 1 + 1 file changed, 1 insertion(+) diff --git a/curl.spec b/curl.spec index 348f6db..9c12786 100644 --- a/curl.spec +++ b/curl.spec @@ -69,6 +69,7 @@ BuildRequires: perl(vars) # #810992, #816175, and #886891). Nevertheless developers are free to install # valgrind manually to improve test coverage on any architecture. %ifarch x86_64 %{ix86} +BuildRequires: glibc-debuginfo BuildRequires: valgrind %endif