Valgrind Fails to Use Debuginfod

N3k0-san commented

2023-07-26 08:42:45 +02:00

Despite being supported, using Valgrind on a compiled AUR package (built with debug info and unstripped) fails with a message about not having access to debug information for dependencies:

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

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.

Happens even if I downgrade Valgrind to upstream Arch's repos

[Despite being supported,](https://wiki.archlinux.org/title/Debuginfod#Debugger_support) using Valgrind on a compiled AUR package (built with debug info and unstripped) fails with a message about not having access to debug information for dependencies: ``` ==294425== Memcheck, a memory error detector ==294425== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al. ==294425== Using Valgrind-3.21.0 and LibVEX; rerun with -h for copyright info ==294425== Command: Cemu ==294425== 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. ``` Happens even if I downgrade Valgrind to upstream Arch's repos

anonfunc commented

2023-08-07 16:58:53 +02:00

Owner

If this happens with vanilla packages its probably an Arch related issue. Not sure if we can do anything from our side here.

anonfunc added the

support

label 2023-09-04 16:47:37 +02:00

averms commented

2024-04-13 10:47:35 +02:00

@N3k0-san what is the output of echo $DEBUGINFOD_URLS? It should have both the ahlp.dev and archlinux.org debuginfod servers.

@N3k0-san what is the output of `echo $DEBUGINFOD_URLS`? It should have both the ahlp.dev and archlinux.org debuginfod servers.

N3k0-san commented

2024-04-15 10:37:56 +02:00

Author

@N3k0-san what is the output of echo $DEBUGINFOD_URLS? It should have both the ahlp.dev and archlinux.org debuginfod servers.

I would actually help with this but I actually moved to Gentoo about 4 months ago, so I can't actually assist with Arch issues anymore because this is my only machine.

> @N3k0-san what is the output of echo $DEBUGINFOD_URLS? It should have both the ahlp.dev and archlinux.org debuginfod servers. I would actually help with this but I actually moved to Gentoo about 4 months ago, so I can't actually assist with Arch issues anymore because this is my only machine.

anonfunc commented

2024-04-17 18:42:39 +02:00

Owner

Since we have no way of verifying this, closing is the best option rn. Please reopen if you experience a similar issue.

anonfunc closed this issue

2024-04-17 18:42:39 +02:00

Valgrind Fails to Use Debuginfod #202