Re: [Valgrind-users] [Valgrind-developers] Valgrind-3.22.0.RC2 is available for testing

[Mark W. <ma...@kl...>]

Hi,

On Thu, Oct 26, 2023 at 12:38:04PM -0700, Carl Love via Valgrind-developers wrote:
> Valgrind-3.22.0.RC2 looks good on power. I have run the RC2 on Power
> 10LE, Power 9 LE, Power 8 LE/BE, and Power 7 BE. I see the two failures
> 
> memcheck/tests/bug340392                 (stderr)
> memcheck/tests/linux/rfcomm              (stderr)
> 
> everywhere which is normal.  A couple of the older systems also report
> 
> memcheck/tests/leak_cpp_interior         (stderr)
> memcheck/tests/linux/sys-execveat        (stderr)
> 
> which is also consistent on those platforms.
> 
> It all looks good on PowerPC.

Thanks.

= I ran make regtest on Fedora 38 POWER9 ppc64le and got:

== 732 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures ==
memcheck/tests/bug340392                 (stderr)
drd/tests/std_thread2                    (stderr)

--- std_thread2.stderr.exp      2023-04-27 15:25:16.109185858 +0000
+++ std_thread2.stderr.out      2023-10-26 23:12:41.571112420 +0000
@@ -1,9 +1,14 @@
 
 Thread 2:
+Conflicting load by thread 2 at 0x........ size 8
+   at 0x........: _dl_new_hash (dl-new-hash.h:90)
+   by 0x........: _dl_lookup_symbol_x (dl-lookup.c:757)
+Allocation context: Data section of /usr/lib64/ld64.so.2
+
 Conflicting store by thread 2 at 0x........ size 4
    at 0x........: main::LAMBDA::operator()() const (std_thread2.cpp:21)
 Allocation context: BSS section of std_thread2
 
 Done.
 
-ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 0 from 0)
+ERROR SUMMARY: 6 errors from 2 contexts (suppressed: 0 from 0)

I haven't really looked into that more. It is a deterministic
failure. But I think data races in ld.so should be suppressed?

= On Fedora 40 (rawhide) x86 (32bit) here are zero failures !

= On Fedora 38 s390x

== 842 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failure, 0 stdoutB failure, 0 post failures ==
memcheck/tests/vbit-test/vbit-test       (stderr)

--- vbit-test.stderr.exp		 2022-02-09 22:47:30.491170867 +0000
+++ vbit-test.stderr.out		 2023-10-26 22:51:38.544254194 +0000
@@ -0,0 +1,3 @@
+Conditional jump or move depends on uninitialised value(s)
+   ...
+

I believe I saw this with 3.21.0 too.

= On RHEL8 x86_64

== 880 tests, 1 stderr failure, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 9 post failures ==
memcheck/tests/overlap                   (stderr)

Which is https://bugs.kde.org/show_bug.cgi?id=402833

Cheers,

Mark