Good evening, I'm trying to debug an issue with Evolution and the Gnome guys asked me to use valgrind. However, when running this command I get an error I'm stuck with: valgrind --num-callers=30 --leak-check=no --track-origins=yes /usr/lib/evolution-calendar-factory -w ==4915== Memcheck, a memory error detector ==4915== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==4915== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info ==4915== Command: /usr/lib/evolution-calendar-factory -w ==4915== 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: strcmp 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. THX Frank
On 24/10/07 06:54PM, Frank wrote:
Good evening,
Hey Frank,
I'm trying to debug an issue with Evolution and the Gnome guys asked me to use valgrind. However, when running this command I get an error I'm stuck with: valgrind --num-callers=30 --leak-check=no --track-origins=yes /usr/lib/evolution-calendar-factory -w
I had a quick look at this on my local machine, but could not get the same debugging setup to work (for me the command just did nothing, so I assume more setup is needed). Are you getting this issue when you also set "--enable-debuginfod=yes" (which should be on by default) while before doing a "export DEBUGINFOD_URLS='https://debuginfod.archlinux.org'"? The debuginfod URL should also be set by default via /etc/profile.d/debuginfod.sh which is installed via libelf. If all that does not help mayb install the glibc debug package from your nearest mirror: sudo pacman -U https://geo.mirror.pkgbuild.com/core-debug/os/x86_64/glibc-debug-2.40%2Br16%... Would be cool to get an update later on if things worked out or didn't work :) Cheers, Chris
==4915== Memcheck, a memory error detector ==4915== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==4915== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info ==4915== Command: /usr/lib/evolution-calendar-factory -w ==4915==
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: strcmp 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.
THX Frank
Am Montag, dem 07.10.2024 um 19:39 +0200 schrieb Christian Heusel:
On 24/10/07 06:54PM, Frank wrote:
I had a quick look at this on my local machine, but could not get the same debugging setup to work (for me the command just did nothing, so I assume more setup is needed). Are you getting this issue when you also set "--enable-debuginfod=yes" (which should be on by default) while before doing a "export DEBUGINFOD_URLS='https://debuginfod.archlinux.org'"?
I didn't know I had st the DEBUGINFOD_URLS
If all that does not help mayb install the glibc debug package from your nearest mirror:
sudo pacman -U https://geo.mirror.pkgbuild.com/core-debug/os/x86_64/glibc-debug-2.40%2Br16%...
Would be cool to get an update later on if things worked out or didn't work :)
Installed the glibc-debug nud now it hangs here ==2642== Memcheck, a memory error detector ==2642== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==2642== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info ==2642== Command: /usr/lib/evolution-calendar-factory -w ==2642== Stopped it after an hour. Frank
On 24/10/07 08:49PM, Frank wrote:
Am Montag, dem 07.10.2024 um 19:39 +0200 schrieb Christian Heusel:
On 24/10/07 06:54PM, Frank wrote:
I had a quick look at this on my local machine, but could not get the same debugging setup to work (for me the command just did nothing, so I assume more setup is needed). Are you getting this issue when you also set "--enable-debuginfod=yes" (which should be on by default) while before doing a "export DEBUGINFOD_URLS='https://debuginfod.archlinux.org'"?
I didn't know I had st the DEBUGINFOD_URLS
If all that does not help mayb install the glibc debug package from your nearest mirror:
sudo pacman -U https://geo.mirror.pkgbuild.com/core-debug/os/x86_64/glibc-debug-2.40%2Br16%...
Would be cool to get an update later on if things worked out or didn't work :)
Installed the glibc-debug nud now it hangs here
I guess now you're in the same boat as I was when testing, maybe you'll need to ask the upstream developers again what they want you to test and tell them that the current command just hangs/does nothing.
==2642== Memcheck, a memory error detector ==2642== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==2642== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info ==2642== Command: /usr/lib/evolution-calendar-factory -w ==2642==
Stopped it after an hour.
Frank
On 07/10/2024 18.54, Frank wrote:
Good evening,
I'm trying to debug an issue with Evolution and the Gnome guys asked me to use valgrind. However, when running this command I get an error I'm stuck with: valgrind --num-callers=30 --leak-check=no --track-origins=yes /usr/lib/evolution-calendar-factory -w ==4915== Memcheck, a memory error detector ==4915== Copyright (C) 2002-2024, and GNU GPL'd, by Julian Seward et al. ==4915== Using Valgrind-3.23.0 and LibVEX; rerun with -h for copyright info ==4915== Command: /usr/lib/evolution-calendar-factory -w ==4915==
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: strcmp valgrind: in an object with soname matching: ld-linux-x86-64.so.2 valgrind: was not found whilst processing
The problem with valgrind on Arch is that you have to update your system first with pacman -Su for valgrind to work. If I remember correclty OS packages must be in sync with corresponding debuginfo packages provided by debuginfod. I do not know the details - maybe there is a subset of packages that needs to be in sync with debuginfo, I just sync them all when I need to use valgrind. Regards, Łukasz
participants (3)
-
Christian Heusel
-
Frank
-
Lukasz Michalski