https://bugs.kde.org/show_bug.cgi?id=495786
Bug ID: 495786
Summary: Valgrind can't find symbols like strlen
Classification: Developer tools
Product: valgrind
Version: 3.24 GIT
Platform: Arch Linux
OS: Linux
Status: REPORTED
Severity: critical
Priority: NOR
Component: general
Assignee: jsew...@acm.org
Reporter: rmbe...@gmail.com
CC: jsew...@acm.org, t...@compton.nu
Depends on: 495761
Target Milestone: ---
+++ This bug was initially created as a clone of Bug #495761 +++
***
If you're not sure this is actually a bug, instead post about it at
https://discuss.kde.org
If you're reporting a crash, attach a backtrace with debug symbols; see
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Please remove this comment after reading and before submitting - thanks!
***
SUMMARY
STEPS TO REPRODUCE
1.
2.
3.
OBSERVED RESULT
EXPECTED RESULT
SOFTWARE/OS VERSIONS
Windows:
macOS:
(available in the Info Center app, or by running `kinfo` in a terminal window)
Linux/KDE Plasma:
KDE Plasma Version:
KDE Frameworks Version:
Qt Version:
ADDITIONAL INFORMATION
This's the output of valgrind:
***
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.so.2
valgrind: was not found whilst processing
valgrind: symbols from the object with soname: ld-linux.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: Note that if you are debugging a 32 bit process on a
valgrind: 64 bit system, you will need a corresponding 32 bit debuginfo
valgrind: package (e.g. libc6-dbg:i386).
valgrind:
valgrind: Cannot continue -- exiting now. Sorry.
***
The system used is Archlinux 32 bits.
Have the same result with Valgrind of the system and compiled from the source
code. I'm use the source code of 3.24 with this line:
```
LD_LIBRARY_PATH=/opt/MV1/usr/lib/valgrind/lib/ /opt/MV1/usr/bin/valgrind
```
This error are persisted by years and appear from the 3.23 of valgrind.
==========================================
IT'S A BUG!!!! NOT RESOLVED!!!
my libraries already have debug info, even i compile it and use the new
libraries with LD_LIBRARY_PATH=, and also export debug info and use
----extra-debuginfo-path=
NEVER WORK!!
Referenced Bugs:
https://bugs.kde.org/show_bug.cgi?id=495761
[Bug 495761] Valgrind can't find symbols like strlen
--
You are receiving this mail because:
You are watching all bug changes.
