valgrind - OpenSUSE 11.2

English Applications
#1

Valgrind doesn’t work on OpenSUSE 11.2.

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.
valgrind:
valgrind: Cannot continue – exiting now. Sorry.

Is there any chance to use it?

Greetings,
Max

#2

I tried looking for a debuginfo package for glibc, but didn’t see one in any of the usual repos.

Valgrind not working is a big deal if OpenSUSE is going to be a legitimate development platform. Has anyone found a resolution to this?

Nathan

#3

On 11/24/2009 05:46 AM, SurplusIguana wrote:
>
> I tried looking for a debuginfo package for glibc, but didn’t see one in
> any of the usual repos.

http://download.opensuse.org/debug/distribution/11.2/

>
> Valgrind not working is a big deal if OpenSUSE is going to be a
> legitimate development platform. Has anyone found a resolution to this?
>
> Nathan
>

turn out, AFAIK looking from google, this is not only openSUSE
problem. btw, you just need to install glibc-debuginfo only.

#4

Thanks, I’ve solved.
Take a look here

Greetings,
Max

#5

I have this problem. I have installed glibc-debuginfo but I still get the same error
==26267== Memcheck, a memory error detector
==26267== Copyright (C) 2002-2009, and GNU GPL’d, by Julian Seward et al.
==26267== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==26267== Command: ./csound /tmp/Stockhausen-Studie_II_engl.csd -o test.wav --old-parser -R
==26267==

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.
valgrind:
valgrind: Cannot continue – exiting now. Sorry.

#6

Has there been any more progress on this? I went to the other threads and downloaded and installed the debuginfo package but still get the same error. Anything else to try?

#7

I do hope this can be resolved. “Lubkily” I did not upgrade one machine to 11.2 as I was short of time, and that means I still have a working valgrind, but that is very incomvenient. Installing the extra package just made no difference on AMD64 machines.

We are holding off upgrading other computers until the valgrind issue is fixed or patched.

==John ff

#8

they have put up debuginfo in 11.2 repo
installed it and valgrind works fine

#9

It does indeed seem to work now, for which I am very grateful. Maybe time to upgrade the 11.1 machines.
==John ff

#10

installed the debuginfo package and valgrind still doesn’t work

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.
valgrind:
valgrind: Cannot continue – exiting now. Sorry.

#11

valgrind is working fine here - openSUSE 11.2 32bit with glibc, glibc-devel, glibc-info glibc-locale installed.

#12

That was mu experience at first; I installed the glibc debuginfo package and it made no difference. Then a few days ago it started to work, and just now on this machien it was broken, installed the debuginfo package and it works. I have version 2.10.1-10.4-x86_64 fronm openSUSE-11.2-Debug installed now.
==John ff

#13

==5215== Memcheck, a memory error detector
==5215== Copyright (C) 2002-2009, and GNU GPL’d, by Julian Seward et al.
==5215== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==5215== Command: /home/gal/workspace/assignment2/Debug/assignment2
==5215==

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.
valgrind:
valgrind: Cannot continue – exiting now. Sorry.

the file ld-linux-x86-64.so.2 doesn’t exist.
i managed to get it to work once when i installed a different version of x11 packs, but that caused my plasma desktop to crash on boot and i would get a black screen. i couldn’t revert it because too many packages were replaced. I reinstalled opensuse.

the glibc packages don’t help. any idea how this could be fixed?

#14

On this machine…

harvey:~> ls -l /lib64/ld-linux-x86-64.so.2
lrwxrwxrwx 1 root root 12 2009-11-18 14:08 /lib64/ld-linux-x86-64.so.2 -> ld-2.10.1.so*
harvey:~> rpm -q -f /lib64/ld-linux-x86-64.so.2
glibc-2.10.1-10.4.x86_64

That package is provides by openSYSE-11.2-Oss
in my case from Index of /distribution/11.2/repo/oss

==John ff

#15

i got exactly the same. but i get the strlen error.

#16

I am getting even more confused. Do you have the package glibc-debuginfo from openSUS-11.2-Debug ??

I have version 2.10.1-10.4x86_64

==John ff

#17

i installed and removed cuz it didnt help
the valgrind-debuginfo is installed

also:

> ls /lib64/ld*
ld-2.10.1.so ld-linux-x86-64.so.2

> rpm -q -f /lib64/ld-linux-x86-64.so.2
glibc-2.10.1-10.4.x86_64

> nm /lib64/ld-2.10.1.so
nm: /lib64/ld-2.10.1.so: no symbols

> ls -l /lib64/ld-linux-x86-64.so.2
lrwxrwxrwx 1 root root 12 2009-12-24 21:50 /lib64/ld-linux-x86-64.so.2 -> ld-2.10.1.so

right now i don’t have glibc-debuginfo installed

#18

What is the solution to this problem? I’ve tried everything listed in this thread, nothing works, the sought-after library isn’t available at any repositories.

Valgrind is critical to my work. If it won’t work under the OpenSuse distribution, I am so gone.

Please point me to a working solution to this problem, or simply state that you don’t plan to fix it.

#19

But that is what you need! I did eventually get it to run in my machines

#20

The solution that shuLhan gave in the first page of this thread worked for me…