Your message dated Thu, 13 Aug 2015 18:30:42 +0200
with message-id <20150813163042.GA17900@jak-x230>
and subject line Re: Bug#795376: valgrind: Fatal error at startup: a function
redirection [...] cannot be set up
has caused the Debian Bug report #795376,
regarding valgrind: Fatal error at startup: a function redirection [...] cannot
be set up
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
795376: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795376
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: valgrind
Version: 1:3.10.1-4
Severity: grave
Valgrind does not work on a recent system anymore (which went
through the gcc5 transition).
$ valgrind echo
==11398== Memcheck, a memory error detector
==11398== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==11398== Using Valgrind-3.10.1 and LibVEX; rerun with -h for copyright info
==11398== Command: echo
==11398==
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: Cannot continue -- exiting now. Sorry.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (900, 'unstable'), (500, 'buildd-unstable'), (100, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages valgrind depends on:
ii libc6 2.19-19
ii libc6-dbg 2.19-19
Versions of packages valgrind recommends:
ii gdb 7.7.1+dfsg-5
pn valgrind-dbg <none>
Versions of packages valgrind suggests:
pn alleyoop <none>
pn kcachegrind <none>
pn valgrind-mpi <none>
pn valkyrie <none>
-- no debconf information
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.
--- End Message ---
--- Begin Message ---
On Thu, Aug 13, 2015 at 04:11:54PM +0200, Julian Andres Klode wrote:
> Package: valgrind
> Version: 1:3.10.1-4
> Severity: grave
>
> Valgrind does not work on a recent system anymore (which went
> through the gcc5 transition).
Nevermind, this was caused by merging /lib into /usr/lib (and
/bin into /usr/bin) and stuff by the usrmerge package that is
in development.
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
Be friendly, do not top-post, and follow RFC 1855 "Netiquette".
- If you don't I might ignore you.
--- End Message ---
