Valgrind cannot run with the glibc provided for Ubuntu 13.10 - where do I report this

Asked by Martin Pagh Goodwin on 2013-11-18

When trying to run valgrind with our project unit tests, it fails with the following message:

==19773== Memcheck, a memory error detector
==19773== Copyright (C) 2002-2012, and GNU GPL'd, by Julian Seward et al.
==19773== Using Valgrind-3.8.1 and LibVEX; rerun with -h for copyright info
==19773== Command: ./gtest
==19773==

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.

Installing libc6-dbg does not fix the issue. It seems that strlen has been inlined in the ubuntu build of glibc, and thus installing the debug symbols does not help.

A bug has been filed against valgrind and glibc in launchpad/Ubuntu, but neither project uses launcpad for bug tracking, and the bug seems to be in Ubuntus usage of glibc, thus not actually an upstream bug.

Where do I go now?

Martin

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu glibc Edit question
Assignee:
No assignee Edit question
Last query:
2013-11-18
Last reply:
2013-11-19

If you run:

ubuntu-bug valgrind

You can report the issue.

but as I wrote, the valgrind team does not use launchpad for bugtracking (if it is even really a valgrind bug)

So basically I'd like some way of promoting the bug - adding better info, or calling someones attention to it (nicely), etc.

Dimitri John Ledkov (xnox) said : #4

you reported the bug in the correct place against "valgrind Ubuntu package". Where "valgrind Upstream" tracks bugs I don't know. But it is probably not launchpad questions =) worth emailing upstream mailing list about it.

Manfred Hampl (m-hampl) said : #5

The "valgrind upstream" bug tracking is on the kde bug pages https://bugs.kde.org/buglist.cgi?product=valgrind and there is already a bug report existing about that strlen problem https://bugs.kde.org/show_bug.cgi?id=286864

Yes - that was also referred in the original bug posting, but that bug is several years old, and the "(mis)feature" has only recently appeared in ubuntu/kubuntu.

The upshot of this is that valgrind does not work, but it does not seem to be a valgrind problem, unless the debug symbols installed with -dbg do actually contain strlen, but are not found - I somehow doubt this, as you cannot provide symbols for an inlined method, and thus the issue becomes one of _how_ glibc is built, which is much harder to move forward...

I appreciate the attention my question is getting, I just don't feel that I am getting much closer to the target of having a working valgrind in ubuntu again - the package might as well not be available in its current state.

Manfred Hampl (m-hampl) said : #7

If you need a working version of valgrind on your Ubuntu system, there should be the possibility of building valgrind from source with the patch https://bugs.kde.org/attachment.cgi?id=82043 added.

Can you help with this problem?

Provide an answer of your own, or ask Martin Pagh Goodwin for more information if necessary.

To post a message you must log in.