Debian Question posted in
The oficial documentation can be found here.

How to fix the fatal error at startup in valgrind (connected with libc6-dbg and libc6-dbg:i386 ) – Debian

Have this problem that can’t fix any way. I tried to install libc6-dbg and libc6-dbg:i386 and it didn’t help.(I have 64 bit Ubuntu 19.10).

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, show you installed packages. As you see everything is correctly installed, but doesn’ work. I don’t know what to do more to make it work.

package for amd64

Package: libc6-dbg
Status: install ok installed
Priority: optional
Section: debug
Installed-Size: 44570
Maintainer: Ubuntu Developers <[email protected]>
Architecture: amd64
Multi-Arch: same
Source: glibc
Version: 2.30-0ubuntu2
Provides: libc-dbg
Depends: libc6 (= 2.30-0ubuntu2)
Description: GNU C Library: detached debugging symbols
 This package contains the detached debugging symbols for the GNU C
 library.
Homepage: https://www.gnu.org/software/libc/libc.html
Original-Maintainer: GNU Libc Maintainers <[email protected]>

package for i386

Package: libc6-dbg
Status: install ok installed
Priority: optional
Section: debug
Installed-Size: 35315
Maintainer: Ubuntu Developers <[email protected]>
Architecture: i386
Multi-Arch: same
Source: glibc
Version: 2.30-0ubuntu2
Provides: libc-dbg
Depends: libc6 (= 2.30-0ubuntu2)
Description: GNU C Library: detached debugging symbols
 This package contains the detached debugging symbols for the GNU C
 library.
Homepage: https://www.gnu.org/software/libc/libc.html
Original-Maintainer: GNU Libc Maintainers <[email protected]>
Tags:

3

Answers


  1. 0

    I ran into the same problem with Ubuntu 20.04. As user phd has pointed out in their comment, this is a Valgrind bug that has been fixed in commit db07db4c8706d17124a621a254bee1b6f08d2e1d

    You can build valgrind easily by running something like 

    git clone git://sourceware.org/git/valgrind.git
cd valgrind
./autogen.sh
./configure
make -j
sudo make install

    (please don’t run commands as sudo if you’re not sure what they do)

    Login or Signup to reply.
  2. 0

    valgrind is looking for files in the wrong path.

    Ubuntu has a mess in /usr/lib/debug. If you unify /usr/lib/debug/lib and /usr/lib/debug/usr/lib it should work.

    At least, that fixed it for me.

    Login or Signup to reply.
  3. 0 
    apt install -y libc6-dbg

    It worked for me. (Note: without :i386.)
    Possible duplicate of install valgrind, Fatal error at startup.

    Login or Signup to reply.
Please signup or login to give your own answer.

Back To Top
Search