| Summary: | strlen: a must-be-redirected function not found | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Aaron Boxer <boxerab> |
| Component: | memcheck | Assignee: | Julian Seward <jseward> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | mark, pjfloyd |
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| URL: | https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1247026 | ||
| See Also: | https://launchpad.net/bugs/1247026 | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Aaron Boxer
2020-11-08 21:31:41 UTC
(In reply to Aaron Boxer from comment #0) > SUMMARY > > Note: I have installed glibc debug symbols (ubuntu 20) Maybe a Ubuntu packaging issue then? Have you reported it in the distro bug database? > 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: 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. (In reply to Mark Wielaard from comment #1) > (In reply to Aaron Boxer from comment #0) > > SUMMARY > > > > Note: I have installed glibc debug symbols (ubuntu 20) > > Maybe a Ubuntu packaging issue then? Have you reported it in the distro bug > database? Good idea, I will do that. I guess there are no work arounds ? > > > 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: 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. Bug open on this since 2011 :) https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1247026?comments=all Looks like a downstream, Ubuntu bug. By some miracle, this issue has no gone way on my system. Either a glibc update, or a valgrind update. ... issue has now gone away |