From yesterday (Indian Standard Time), Valgrind doesn’t work, the problem is with glibc version. Testing and Stable Branch is providing glibc 2.37.2 but Arch version is at 2.37.3, and for that reason valgrind cannot find debug symbols.
I wanted to ask When glibc 2.37.3 will be available for Testing or Stable, this is really creating a mess for me. Thank you.
Here’s valgrind output
==4781== Memcheck, a memory error detector ==4781== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==4781== Using Valgrind-3.20.0-5147d671e4-20221024 and LibVEX; rerun with -h for copyright info ==4781== Command: ./bnmain ==4781== --4781-- Valgrind options: --4781-- -v --4781-- -s --4781-- --leak-check=full --4781-- --show-leak-kinds=all --4781-- --track-origins=yes --4781-- Contents of /proc/version: --4781-- Linux version 6.2.12-1-MANJARO (builduser@fv-az302-253) (gcc (GCC) 12.2.1 20230201, GNU ld (GNU Binutils) 2.40) #1 SMP PREEMPT_DYNAMIC Thu Apr 20 14:17:37 UTC 2023 --4781-- --4781-- Arch and hwcaps: AMD64, LittleEndian, amd64-cx16-lzcnt-rdtscp-sse3-ssse3-avx-avx2-bmi-f16c-rdrand-rdseed --4781-- Page sizes: currently 4096, max supported 4096 --4781-- Valgrind library directory: /usr/lib/valgrind --4781-- Reading syms from /home/palash/d/baurinum/bnmain --4781-- Reading syms from /usr/lib/ld-linux-x86-64.so.2 ==4781== Downloading debug info for /usr/lib/ld-linux-x86-64.so.2... ==4781== Server query failed: No such file or directory --4781-- object doesn't have a symbol table 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.