Arch Linux

Please read this before reporting a bug:

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!

FS#74755 - [glibc] Valgrind shows that it doesn't have file.

Attached to Project: Arch Linux
Opened by Przemek (Fuchczyk) - Sunday, 15 May 2022, 14:31 GMT
Last edited by freswa (frederik) - Sunday, 15 May 2022, 16:04 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To freswa (frederik)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No


Valgrind doesn't even start - it shows error message shown below.
It started after update of glibc. Tried reinstalling and building from source.

==49201== Memcheck, a memory error detector
==49201== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==49201== Using Valgrind-3.19.0 and LibVEX; rerun with -h for copyright info
==49201== Command: ls

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: A must-be-redirected function
valgrind: whose name matches the pattern: strlen
valgrind: in an object with soname matching:
valgrind: was not found whilst processing
valgrind: symbols from the object with soname:
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 (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: On Debian, Ubuntu: libc6-dbg
valgrind: On SuSE, openSuSE, Fedora, RHEL: glibc-debuginfo
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: Cannot continue -- exiting now. Sorry.


debuginfod-0.187-1 (in case if needed)

Steps to reproduce:
1. Run any command under control of valgrind, eg. valgrind ls.
This task depends upon

Closed by  freswa (frederik)
Sunday, 15 May 2022, 16:04 GMT
Reason for closing:  Not a bug
Additional comments about closing:  $DEBUGINFOD_URLS needs to be set in order to be able to fetch debug pkgs. Source /etc/profile.d/ or logout once.
Comment by freswa (frederik) - Sunday, 15 May 2022, 15:39 GMT
Have you created a fresh shell after you installed debuginfod?
What is the output of `echo $DEBUGINFOD_URLS`?
Comment by Przemek (Fuchczyk) - Sunday, 15 May 2022, 15:55 GMT
I have created a fresh shell. My DEBUGINFOD_URLS has none value, but after setting it to 1, everything works. Sorry for bothering You and thanks for Your help.
Comment by freswa (frederik) - Sunday, 15 May 2022, 16:00 GMT
Sourcing /etc/profile.d/ or /etc/profile.d/debuginfod.csh should help out until the next logout.