On 19 February 2014 13:23, Tom Hughes <t...@compton.nu> 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 (t...@compton.nu) > 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 ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471&iu=/4140/ostg.clktrk _______________________________________________ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
