I have started running valgrind on valgrind (outer/inner setup).
Results should be available tomorrow evening or so ...
For the first few tests, seems ok.
Just one strange thing:
The outer valgrind crashes on the below test (while the native run of this test
is ok).
(this is on gcc farm gcc186).
Not very clear to me how the ld-linux.so.2 redirection could be ok in native
mode,
but would not be ok when the same valgrind runs as an outer.
In any case, this is not blocking.
More complete results will follow ...
Philippe
cachegrind/tests/x86/fpu-28-108.outer.log:10:valgrind: Fatal error at startup:
a function redirection
cachegrind/tests/x86/fpu-28-108.outer.log:11:valgrind: which is mandatory for
this platform-tool combination
cachegrind/tests/x86/fpu-28-108.outer.log:12:valgrind: cannot be set up.
Details of the redirection are:
cachegrind/tests/x86/fpu-28-108.outer.log:13:valgrind:
cachegrind/tests/x86/fpu-28-108.outer.log:14:valgrind: A must-be-redirected
function
cachegrind/tests/x86/fpu-28-108.outer.log:15:valgrind: whose name matches the
pattern: strlen
cachegrind/tests/x86/fpu-28-108.outer.log:16:valgrind: in an object with
soname matching: ld-linux.so.2
cachegrind/tests/x86/fpu-28-108.outer.log:17:valgrind: was not found whilst
processing
cachegrind/tests/x86/fpu-28-108.outer.log:18:valgrind: symbols from the object
with soname: ld-linux.so.2
cachegrind/tests/x86/fpu-28-108.outer.log:19:valgrind:
cachegrind/tests/x86/fpu-28-108.outer.log:20:valgrind: Possible fixes: (1,
short term): install glibc's debuginfo
cachegrind/tests/x86/fpu-28-108.outer.log:21:valgrind: package on this
machine. (2, longer term): ask the packagers
cachegrind/tests/x86/fpu-28-108.outer.log:22:valgrind: for your Linux
distribution to please in future ship a non-
cachegrind/tests/x86/fpu-28-108.outer.log:23:valgrind: stripped ld.so (or
whatever the dynamic linker .so is called)
cachegrind/tests/x86/fpu-28-108.outer.log:24:valgrind: that exports the
above-named function using the standard
cachegrind/tests/x86/fpu-28-108.outer.log:25:valgrind: calling conventions for
this platform. The package you need
cachegrind/tests/x86/fpu-28-108.outer.log:26:valgrind: to install for fix (1)
is called
cachegrind/tests/x86/fpu-28-108.outer.log:27:valgrind:
cachegrind/tests/x86/fpu-28-108.outer.log:28:valgrind: On Debian, Ubuntu:
libc6-dbg
cachegrind/tests/x86/fpu-28-108.outer.log:29:valgrind: On SuSE, openSuSE,
Fedora, RHEL: glibc-debuginfo
cachegrind/tests/x86/fpu-28-108.outer.log:30:valgrind:
cachegrind/tests/x86/fpu-28-108.outer.log:31:valgrind: Note that if you are
debugging a 32 bit process on a
cachegrind/tests/x86/fpu-28-108.outer.log:32:valgrind: 64 bit system, you will
need a corresponding 32 bit debuginfo
cachegrind/tests/x86/fpu-28-108.outer.log:33:valgrind: package (e.g.
libc6-dbg:i386).
cachegrind/tests/x86/fpu-28-108.outer.log:34:valgrind:
cachegrind/tests/x86/fpu-28-108.outer.log:35:valgrind: Cannot continue --
exiting now. Sorry.
On Thu, 2022-10-20 at 01:52 +0200, Mark Wielaard wrote:
> Greetings.
>
> A first release candidate for 3.20.0 is available at
> https://sourceware.org/pub/valgrind/valgrind-3.20.0.RC1.tar.bz2
> (md5 = 981b9276536843090700c1268549186e)
>
> Please give it a try on platforms that are important for you. If no
> serious issues are reported, the 3.20.0 final release will happen on
> 22 October.
>
>
>
> _______________________________________________
> Valgrind-developers mailing list
> valgrind-develop...@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users
