|
From: Robin <rc....@gm...> - 2014-02-19 12:56:40
|
Linux localhost 3.11-2-amd64 #1 SMP Debian 3.11.10-1 (2013-12-04) x86_64 GNU/Linux Debian GNU/Linux unstable (sid) Multiarch Full error: 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. Paths to dbg: /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.17.so /usr/lib/debug/lib/i386-linux-gnu/ld-2.17.so Do I need to create a link ld-linux-x86-64.so.2, somewhere, pointing to the ld-2.17.so? Thanks -- rob |
|
From: Tom H. <to...@co...> - 2014-02-19 13:24:05
|
On 19/02/14 12:56, Robin wrote: > Paths to dbg: > /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.17.so > /usr/lib/debug/lib/i386-linux-gnu/ld-2.17.so Note that installing the debug package is only a possible fix - we have no way of knowing for sure whether it will work on any particular OS. What I'm not clear about though is what happens without libc6-dbg - the subject of your mail implies that it only breaks when you have that installed? So does it work when you don't have it? > Do I need to create a link ld-linux-x86-64.so.2, somewhere, pointing > to the ld-2.17.so? No, that would be a really bad idea. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: Robin <rc....@gm...> - 2014-02-19 13:47:48
|
On 19 February 2014 13:23, Tom Hughes <to...@co...> wrote: > On 19/02/14 12:56, Robin wrote: > >> Paths to dbg: >> /usr/lib/debug/lib/x86_64-linux-gnu/ld-2.17.so >> /usr/lib/debug/lib/i386-linux-gnu/ld-2.17.so > > > Note that installing the debug package is only a possible fix - we have no > way of knowing for sure whether it will work on any particular OS. > > What I'm not clear about though is what happens without libc6-dbg - the > subject of your mail implies that it only breaks when you have that > installed? So does it work when you don't have it? > > >> Do I need to create a link ld-linux-x86-64.so.2, somewhere, pointing >> to the ld-2.17.so? > > > No, that would be a really bad idea. > > Tom > > -- > Tom Hughes (to...@co...) > http://compton.nu/ Thanks for the reply In Debian Valgrind has a required dependency of libc6-dbg. So I removed the deb package and installed from source. Same error message without libc6-dbg installed. It was last working a 2 or 3 months ago, when I getting info for a bug report. Valgrind version, by the way, is 3.9.0 deb package and source. Thanks -- rob |
|
From: Tom H. <to...@co...> - 2014-02-19 14:11:21
|
On 19/02/14 13:47, Robin wrote: > In Debian Valgrind has a required dependency of libc6-dbg. So I > removed the deb package and installed from source. > Same error message without libc6-dbg installed. > > It was last working a 2 or 3 months ago, when I getting info for a bug report. > > Valgrind version, by the way, is 3.9.0 deb package and source. Right, so it sounds like you need to be talking to the maintainers of valgrind and/or libc in Debian then. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |