| Summary: | app-metrics/collectd-5.7.2 : FAIL: test_common | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | kentnl, wizardedit |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | was: dev-util/valgrind cannot trace any executables ( function redirection ... cannot be set up ) | ||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
emerge-info.txt
app-admin:collectd-5.7.2:20170919-041800.log emerge-history.txt environment etc.portage.tbz2 logs.tbz2 temp.tbz2 logdiff Passing tests on ~amd64 |
||
|
Description
Toralf Förster
2017-09-19 07:28:29 UTC
Created attachment 495362 [details]
emerge-info.txt
Created attachment 495364 [details]
app-admin:collectd-5.7.2:20170919-041800.log
Created attachment 495366 [details]
emerge-history.txt
Created attachment 495368 [details]
environment
Created attachment 495370 [details]
etc.portage.tbz2
Created attachment 495372 [details]
logs.tbz2
Created attachment 495374 [details]
temp.tbz2
I cannot reproduce. Please either attach all test logs or tests/ directory. Failure is
> FAIL: test_common
> =================
>
>
> 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.
>
> FAIL test_common (exit status: 1)
I cannot reproduce yet. Could this be a platform issue caused by your chroot environment?
Created attachment 496416 [details, diff]
logdiff
I can replicate this, would have filed a bug hours ago but I had to rebuild perl to be sure.
I have the ability to give you a log from last month that passed, and one that failed today, so their differences might be indicative.
=app-admin/collectd-5.6.2-r4
=app-admin/collectd-5.7.1
=app-admin/collectd-5.7.2
All failed 100%
Ansi-filtered diff attached.
Also, incidentally, this problem goes away completely without valgrind installed. Created attachment 496420 [details]
Passing tests on ~amd64
Weird. See my attached build.log from my ~amd64 system. Passing tests. Showing that collectd is picking up valgrind as well...
Is valgrind broken on your system?
I did a clean remove of valgrind, tests pass. Install valgrind 3.12.0 from scratch, tests fail. However: valgrind /bin/true ==873533== Memcheck, a memory error detector ==873533== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al. ==873533== Using Valgrind-3.12.0 and LibVEX; rerun with -h for copyright info ==873533== Command: /bin/true ==873533== 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. Upgrading to latest valgrind 3.13.0 also has the same result: ==883062== Memcheck, a memory error detector ==883062== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al. ==883062== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info ==883062== Command: /bin/true ==883062== 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. Reassigning to valgrind team as valgrind is clearly broken on an entirely special level. The link below may be helpful to fix this bug. It could be a simple case of GCC inlining strlen. I have glibc with debugging and nostrip, and still my valgrind is broken. https://wwwtech.de/articles/2012/jan/valgrind-again:-strlen-redirection This is actually not a bug. See https://wiki.gentoo.org/wiki/Debugging#Valgrind That Wiki page doesn't fix the test failures in collectd. I would possibly suggest collectd should disable this test given user configuration and rebuilding glibc is required for it to pass. Since app-metrics/collectd-5.7.2 does not exist anymore in tree, closing here. Please reopen, if problem persists with current version. |