Arch Linux

LienerAruk

Member

Registered: 2022-08-21

Posts: 2

Issues with valgrind [SOLVED]

Valgrind simply prints weird errors and exits when I try to use it like so

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

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.

So I surfed for a solution and got this:

sudo DEBUGINFOD_URLS="https://debuginfod.archlinux.org" G_SLICE=always-malloc valgrind --leak-check=full ls --debug

Which works btw. Now I realised that the path that is that

DEBUGINFOD_URLS

environment variable might not be set, so I tried to echo it, and it was actually set. What the hell is going on? even if I run

sudo G_SLICE=always-malloc valgrind --leak-check=full ls --debug

(I suspected that the G_SLICE env variable might have been an issue) it doesn't run.

Last edited by LienerAruk (2022-08-24 23:32:15)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,265

Re: Issues with valgrind [SOLVED]

sudo will drop a large part of your environment for safety purposes, tell it to keep specific ones, like DEBUGINFOD_URLS https://wiki.archlinux.org/title/Sudo#E … _variables

LienerAruk

Member

Registered: 2022-08-21

Posts: 2

Re: Issues with valgrind [SOLVED]

sudo will drop a large part of your environment for safety purposes, tell it to keep specific ones, like DEBUGINFOD_URLS https://wiki.archlinux.org/title/Sudo#E … _variables

It works man. Thanks

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,265

Re: Issues with valgrind [SOLVED]

Please mark as [SOLVED] by editing the title in your first post.