Hello. Whenever I use valgrind, I get this (on 3 different PCs):
==6657== Memcheck, a memory error detector ==6657== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==6657== Using Valgrind-3.20.0 and LibVEX; rerun with -h for copyright info ==6657== Command: ./src/Tests/save-osc test-all ==6657== 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.
My system info:
$ pacman -Q glibc valgrind glibc 2.37-2 valgrind 3.20.0-1
With gdb, debuginfod works fine.
What I have found so far:
- Cannot use valgrind - They suggest downgrading glibc, but claim that it was fixed in glibc 2.35-6. I’m not sure if downgrading is really a good idea, if the new version should already support it. Even if I downgrade, doesn’t using old software mean that I miss current security updates, which means a security risk?
Valgrind problem after glibc update - They suggest exporting
DEBUGINFOD_URLS="https://debuginfod.archlinux.org", but that does not help in my case.
- Unable to use valgrind - Mostly no solution, some people have solved it with upgrading, but their glibc was older than my current glibc.
Can anyone please help? Thanks on advance.