Open FascinatedBox opened 9 years ago
will take a look on that
Tried building a glibc package today with...no luck whatsoever. I managed to get glibc to compile by passing "-fno-stack-protector -U_FORTIFY_SOURCE -O
(after many attempts and it failing to compile with different options).
However, each version of glibc that I try to build crashes complaining about a vdso something or other or just outright crashing.
will try find a way to have it working in few days.
Also happens to me while going through the Learn C The Hard Way book.
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.
Manual install also does not work.
$ make install
make install-recursive
make[1]: Entering directory `/home/codio/workspace/valgrind-3.10.1'
Making install in include
make[2]: Entering directory `/home/codio/workspace/valgrind-3.10.1/include'
make[3]: Entering directory `/home/codio/workspace/valgrind-3.10.1/include'
make[3]: Nothing to be done for `install-exec-am'.
/bin/mkdir -p '/usr/local/include/valgrind'
/bin/mkdir: cannot create directory `/usr/local/include/valgrind': Permission denied
make[3]: *** [install-nobase_pkgincludeHEADERS] Error 1
make[3]: Leaving directory `/home/codio/workspace/valgrind-3.10.1/include'
make[2]: *** [install-am] Error 2
make[2]: Leaving directory `/home/codio/workspace/valgrind-3.10.1/include'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/codio/workspace/valgrind-3.10.1'
make: *** [install] Error 2
So...I tried running valgrind today on one of my programs. This is the result.
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.
This error seems to trigger no matter what I try: /bin/ls, /bin/true/, /bin/cd, etc.
Would creating a package for libc6 fix this, perhaps? If so, I'll gladly make it because I really would like to see valgrind working.