> On 27 Oct 2023, at 00:54, Mark Wielaard <m...@klomp.org> wrote:
> 
> 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?

That’s right. Any non-pthread locking mechanisms in libc libpthread ld.so that 
generates errors should be suppressed (we assume that these libraries are 
correct, they would need annotation otherwise).

A+
Paul


_______________________________________________
Valgrind-users mailing list
Valgrind-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/valgrind-users

Reply via email to