Test results look fairly good on the platforms I tested.
I did fix a couple of small (testcase) issues for x86:
32 bit new_delete_mismatch_size and sized_aligned_new_delete_misaligned .exp
and s390x:
filter out in /absolute/path in drd/tests stderr filter
With those:
RHEL 8.9/x86-64:
== 896 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
Fedora 39/s390x
== 857 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
drd/tests/bar_bad_xml (stderr)
drd/tests/getaddrinfo (stderr)
Those two tests are flaky and not always failing.
Fedora ELN x86_64 (this distro is build with -march=x86_64-v3)
== 808 tests, 0 stderr failures, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
Debian 12.5/arm64
== 727 tests, 8 stderr failures, 0 stdout failures, 0 stderrB failures, 1
stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
memcheck/tests/dw4 (stderr)
memcheck/tests/varinfo2 (stderr)
memcheck/tests/varinfo4 (stderr)
memcheck/tests/varinfo5 (stderr)
memcheck/tests/varinfo6 (stderr)
memcheck/tests/varinforestrict (stderr)
helgrind/tests/hg05_race2 (stderr)
helgrind/tests/tc20_verifywrap (stderr)
Almost all are backtrace issues or stack/thread frame issues like
- Location 0x........ is 0 bytes inside local var "rwl2"
- declared at tc20_verifywrap.c:58, in frame #x of thread x
+ Address 0x........ is on thread #x's stack
+ in frame #x, created by main (tc20_verifywrap.c:49)
Fedora 38/ppc64le
== 744 tests, 4 stderr failures, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
drd/tests/bar_bad (stderr)
drd/tests/bar_bad_xml (stderr)
drd/tests/std_thread2 (stderr)
none/tests/socket_close (stderr)
bar_bad tests seems flaky.
drd/tests/std_thread2 might need a suppression
+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
socket_close looks like the backtrace is skipping main for some reason
at 0x........: socket (in /...libc...)
by 0x........: open_socket (socket_close.c:17)
- by 0x........: main (socket_close.c:31)
+ by 0x........: (below main)
Fedora 40/i386
== 801 tests, 1 stderr failures, 0 stdout failures, 0 stderrB failures, 0
stdoutB failures, 0 post failures ==
memcheck/tests/x86-linux/scalar (stderr)
Debian 12.5/i686
== 798 tests, 12 stderr failures, 2 stdout failures, 0 stderrB failures, 0
stdoutB failures, 1 post failure ==
memcheck/tests/close_range (stderr)
memcheck/tests/linux/rfcomm (stderr)
memcheck/tests/sendmsg (stderr)
memcheck/tests/sized_aligned_new_delete_misaligned3_supp (stderr)
memcheck/tests/x86/insn_basic (stdout)
memcheck/tests/x86/insn_basic (stderr)
memcheck/tests/x86-linux/scalar (stderr)
helgrind/tests/pth_mempcpy_false_races (stderr)
drd/tests/bar_bad (stderr)
massif/tests/mmapunmap (post)
none/tests/fdleak_ipv4 (stderr)
none/tests/file_dclose (stderr)
none/tests/socket_close (stderr)
none/tests/x86/insn_basic (stdout)
none/tests/x86/insn_basic (stderr)
Haven't analyzed fully but there are clearly more failures than on
Fedora i386. Some are just things like an extra frame:
+ at 0x........: _dl_sysinfo_int80 (in /usr/lib/i386-linux-gnu/ld-linux.so.2)
_______________________________________________
Valgrind-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/valgrind-users
