Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing
On Sun, 2022-10-23 at 00:11 +0200, Mark Wielaard wrote: > Hi Philippe, > > On Sat, Oct 22, 2022 at 02:58:28PM +0200, Philippe Waroquiers wrote: > > 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 ... > > Thanks. I have no theory for the outer valgrind crash. But it doesn't > seem blocking indeed. I am also still running some tests. Please let > me know of further results. And do the actual release on Monday > (unless some regression blocker turns up). > > Cheers, > > Mark > For the crash of the outer valgrind: there is in fact some debug info really missing on gcc186 (also for the inner) for the 32 bits version. I have looked at the results of this outer/inner setup and found nothing that seems problematic. Note that analysis the outer logs is always painful, as the outer reports as "bugs" the fact the inner uses e.g. some invalid memory because the guest program run by the inner is designed to test the usage of such invalid memory. Thanks Philippe ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing
Hi Philippe, On Sat, Oct 22, 2022 at 02:58:28PM +0200, Philippe Waroquiers wrote: > 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 ... Thanks. I have no theory for the outer valgrind crash. But it doesn't seem blocking indeed. I am also still running some tests. Please let me know of further results. And do the actual release on Monday (unless some regression blocker turns up). Cheers, Mark ___ Valgrind-users mailing list Valgrind-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/valgrind-users
Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing
Hi,
On Thu, Oct 20, 2022 at 01:25:44PM -0700, Carl Love wrote:
> The only issue noted, as discussed on #valgrind-dev channel, is the
> addition of four post errors for the 3.20RC tree on all of the Power
> platforms. Specifically:
>
> cachegrind/tests/ann1(post)
> cachegrind/tests/ann2(post)
> callgrind/tests/ann1 (post)
> callgrind/tests/ann2 (post)
>
> The output from cachegrind/tests/ann1.post.diff is:
>
> --- ann1.post.exp 2021-01-21 09:09:33.0 -0600
> +++ ann1.post.out 2022-10-20 14:07:33.272141328 -0500
> @@ -33,6 +33,13 @@
>
> ---
> -
> -- Auto-annotated source: a.c
>
> ---
> -
> +@@
> @
> +@@ WARNING @@ WARNING @@ WARNING @@ WARNING @@ WARNING @@ WARNING @@
> WARNING @@
> +@@
> @
> +@ Source file 'a.c' is more recent than input file 'cgout-test'.
> +@ Annotations may not be correct.
> +@@
> @
> +
> IrI1mr ILmr
>
> 200 int main(void) {
>
> As discussed on the #valgrind-dev channel, this appears to be a
> timestamp issue. Doing a touch * in directory cachegrind/tests seems
> to fix all four post errors.
>
> No other issues were noted. I would vote to do the touch * command and
> go ahead with the release.
I added the touch to the testcases as attached. That makes sure the
cgout-test file is always newer.
Cheers,
Mark
>From 206dbcfed93f22370e03a03dd07f14ab675e24a8 Mon Sep 17 00:00:00 2001
From: Mark Wielaard
Date: Sat, 22 Oct 2022 17:29:00 +0200
Subject: [PATCH] {callgrind,callgrind}/tests/ann{1,2}.vgtest touch cgout-test
Both a.c and cgout-test are checked into the repository and
used in testcases. Make sure cgout-test is newer than a.c
before running the post script to prevent warnings liks:
@@ WARNING @@ WARNING @@ WARNING @@ WARNING @@ WARNING @@ WARNING @@
@ Source file 'a.c' is more recent than input file
../../cachegrind/tests/cgout-test'.
@ Annotations may not be correct.
---
cachegrind/tests/ann1.vgtest | 2 +-
cachegrind/tests/ann2.vgtest | 2 +-
callgrind/tests/ann1.vgtest | 2 +-
callgrind/tests/ann2.vgtest | 2 +-
4 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/cachegrind/tests/ann1.vgtest b/cachegrind/tests/ann1.vgtest
index 676fe3199..e3e574276 100644
--- a/cachegrind/tests/ann1.vgtest
+++ b/cachegrind/tests/ann1.vgtest
@@ -2,5 +2,5 @@
# the post-processing of the cgout-test file.
prog: ../../tests/true
vgopts: --cachegrind-out-file=cachegrind.out
-post: perl ../../cachegrind/cg_annotate --show=Ir,I1mr,ILmr --show-percs=no cgout-test
+post: touch cgout-test && perl ../../cachegrind/cg_annotate --show=Ir,I1mr,ILmr --show-percs=no cgout-test
cleanup: rm cachegrind.out
diff --git a/cachegrind/tests/ann2.vgtest b/cachegrind/tests/ann2.vgtest
index 5acc68b8d..14ccd24db 100644
--- a/cachegrind/tests/ann2.vgtest
+++ b/cachegrind/tests/ann2.vgtest
@@ -2,5 +2,5 @@
# the post-processing of the cgout-test file.
prog: ../../tests/true
vgopts: --cachegrind-out-file=cachegrind.out
-post: perl ../../cachegrind/cg_annotate --sort=Dr --show=Dw,Dr,Ir --auto=yes cgout-test
+post: touch cgout-test && perl ../../cachegrind/cg_annotate --sort=Dr --show=Dw,Dr,Ir --auto=yes cgout-test
cleanup: rm cachegrind.out
diff --git a/callgrind/tests/ann1.vgtest b/callgrind/tests/ann1.vgtest
index 4ad9ae390..3c53e1f55 100644
--- a/callgrind/tests/ann1.vgtest
+++ b/callgrind/tests/ann1.vgtest
@@ -2,5 +2,5 @@
# the post-processing of the cgout-test file.
prog: ../../tests/true
vgopts: --callgrind-out-file=callgrind.out
-post: perl ../../callgrind/callgrind_annotate --show=Ir,I1mr,ILmr --show-percs=no --include=../../cachegrind/tests ../../cachegrind/tests/cgout-test
+post: touch ../../cachegrind/tests/cgout-test && perl ../../callgrind/callgrind_annotate --show=Ir,I1mr,ILmr --show-percs=no --include=../../cachegrind/tests ../../cachegrind/tests/cgout-test
cleanup: rm callgrind.out
diff --git a/callgrind/tests/ann2.vgtest b/callgrind/tests/ann2.vgtest
index 30e177907..9b7dffa0f 100644
--- a/callgrind/tests/ann2.vgtest
+++ b/callgrind/tests/ann2.vgtest
@@ -2,5 +2,5 @@
# the post-processing of the cgout-test file.
prog: ../../tests/true
vgopts: --callgrind-out-file=callgrind.out
-post: perl ../../callgrind/callgrind_annotate --sort=Dr --show=Dw,Dr,Ir --auto=yes --include=../../cachegrind/tests ../../cachegrind/tests/cgout-test
+post: touch ../../cachegrind/tests/cgout-test && perl ../../callgrind/callgrind_annotate --sort=Dr --show=Dw,Dr,Ir
Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.20.0.RC1 is available for testing
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
