|
From: Mark W. <ma...@kl...> - 2019-04-08 19:47:44
|
Hi, On Mon, 2019-04-08 at 11:11 +0200, Julian Seward wrote: > A first release candidate for 3.15.0 is available at > https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC1.tar.bz2 > (md5 = 56d9f5e25615d48110da0aa5764d481e) > > Please give it a try on platforms that are important for you. If no serious > issues are reported, the 3.15.0 final release will happen on 12 April, that > is, this coming Friday. I build and ran regtest on amd64, arm64, ppc64le and s390x with gcc 8.2.1, binutils 2.30, glibc-2.28, linux 4.18.0 and gdb 8.2. Unfortunately for some tests I only have the results not the actual diffs (anymore). amd64 ----- == 710 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures, 2 stdoutB failures, 4 post failures == gdbserver_tests/mcsignopass (stdoutB) gdbserver_tests/mcsigpass (stdoutB) This seems simply a difference in gdb output, it no longer seems to print the address if it is at the start of a function. Sasha might have a patch for the gdb.filter to make it work with old/new gdb. memcheck/tests/leak_cpp_interior (stderr) Looks like the libstdc++.supp doesn't match precisely anymore, causing an extra unexpected still reachable block. Testing a patch (attached). memcheck/tests/overlap (stderr) https://bugs.kde.org/show_bug.cgi?id=402833 cachegrind/tests/ann1 (post) cachegrind/tests/ann2 (post) callgrind/tests/ann1 (post) callgrind/tests/ann2 (post) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc09_bad_unlock (stderr) exp-sgcheck/tests/stackerr (stderr) I don't have access to these files anymore. arm64 ----- == 624 tests, 20 stderr failures, 4 stdout failures, 0 stderrB failures, 1 stdoutB failure, 4 post failures == gdbserver_tests/hgtls (stdoutB) I don't fully understand this testcase. memcheck/tests/arm64-linux/scalar (stderr) Failed because ran as root (yeah, I know I shouldn't). Then setuid unexpected succeeds... memcheck/tests/dw4 (stderr) memcheck/tests/leak_cpp_interior (stderr) memcheck/tests/supp_unknown (stderr) memcheck/tests/varinfo1 (stderr) memcheck/tests/varinfo2 (stderr) memcheck/tests/varinfo3 (stderr) memcheck/tests/varinfo4 (stderr) memcheck/tests/varinfo5 (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/varinforestrict (stderr) Don't have the diffs handy, but when I looked these all said something like "allocated on thread stack x" instead of "in variable x on stack". cachegrind/tests/ann1 (post) cachegrind/tests/ann2 (post) callgrind/tests/ann1 (post) callgrind/tests/ann2 (post) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc20_verifywrap (stderr) drd/tests/std_thread2 (stderr) exp-sgcheck/tests/bad_percentify (stdout) exp-sgcheck/tests/bad_percentify (stderr) exp-sgcheck/tests/globalerr (stderr) exp-sgcheck/tests/hackedbz2 (stdout) exp-sgcheck/tests/hackedbz2 (stderr) exp-sgcheck/tests/hsg (stdout) exp-sgcheck/tests/hsg (stderr) exp-sgcheck/tests/preen_invars (stdout) exp-sgcheck/tests/preen_invars (stderr) exp-sgcheck/tests/stackerr (stderr) Haven't investigated the diff files. The exp-sgcheck failes looked similar to the memcheck/varinfo testcases (couldn't identify the variable just that it was stack allocated). ppc64le ------- == 644 tests, 3 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 6 post failures == memcheck/tests/bug340392 (stderr) I am not sure this can succeed on ppc64le? memcheck/tests/leak_cpp_interior (stderr) Similar to x86_64, but slightly different. memcheck/tests/linux/rfcomm (stderr) diff looks like: Address 0x........ is on thread 1's stack - in frame #1, created by main (rfcomm.c:26) + in frame #0, created by bind (???:) Uninitialised value was created by a client request at 0x........: main (rfcomm.c:45) cachegrind/tests/ann1 (post) cachegrind/tests/ann2 (post) callgrind/tests/ann1 (post) callgrind/tests/ann2 (post) Not investigated, but probably what Carl reported. massif/tests/new-cpp (post) massif/tests/overloaded-new (post) Probably changes in libstdc++? s390x ----- == 748 tests, 76 stderr failures, 1 stdout failure, 0 stderrB failures, 2 stdoutB failures, 4 post failures == gdbserver_tests/mcsignopass (stdoutB) gdbserver_tests/mcsigpass (stdoutB) Similar to x86_64. memcheck/tests/leak_cpp_interior (stderr) Probably similar to x86_64, but I don't have access to the exact diff. memcheck/tests/memcmptest (stderr) Unknown. memcheck/tests/vbit-test/vbit-test (stderr) memcheck/tests/wrap6 (stdout) This looked bad. But isn't a regression. It also failed with 3.14.0. cachegrind/tests/ann1 (post) cachegrind/tests/ann2 (post) callgrind/tests/ann1 (post) callgrind/tests/ann2 (post) Probably same as ppc64le. drd/tests/annotate_barrier (stderr) drd/tests/annotate_barrier_xml (stderr) drd/tests/annotate_hb_race (stderr) drd/tests/annotate_hbefore (stderr) drd/tests/annotate_ignore_read (stderr) drd/tests/annotate_order_2 (stderr) drd/tests/annotate_order_3 (stderr) drd/tests/annotate_rwlock (stderr) drd/tests/annotate_sem (stderr) drd/tests/annotate_smart_pointer (stderr) drd/tests/annotate_spinlock (stderr) drd/tests/atomic_var (stderr) drd/tests/bar_bad (stderr) drd/tests/bar_bad_xml (stderr) drd/tests/bar_trivial (stderr) drd/tests/bug-235681 (stderr) drd/tests/bug322621 (stderr) drd/tests/circular_buffer (stderr) drd/tests/concurrent_close (stderr) drd/tests/dlopen (stderr) drd/tests/fork-serial (stderr) drd/tests/free_is_write (stderr) drd/tests/free_is_write2 (stderr) drd/tests/hg02_deadlock (stderr) drd/tests/hg03_inherit (stderr) drd/tests/hg04_race (stderr) drd/tests/hg05_race2 (stderr) drd/tests/hg06_readshared (stderr) drd/tests/matinv (stderr) drd/tests/monitor_example (stderr) drd/tests/pth_barrier2 (stderr) drd/tests/pth_barrier3 (stderr) drd/tests/pth_barrier_race (stderr) drd/tests/pth_barrier_thr_cr (stderr) drd/tests/pth_broadcast (stderr) drd/tests/pth_cancel_locked (stderr) drd/tests/pth_cond_race (stderr) drd/tests/pth_cond_race2 (stderr) drd/tests/pth_create_chain (stderr) drd/tests/pth_detached2 (stderr) drd/tests/pth_detached_sem (stderr) drd/tests/pth_inconsistent_cond_wait (stderr) drd/tests/pth_spinlock (stderr) drd/tests/read_and_free_race (stderr) drd/tests/rwlock_race (stderr) drd/tests/rwlock_test (stderr) drd/tests/sem_open2 (stderr) drd/tests/sem_open3 (stderr) drd/tests/sem_open_traced (stderr) drd/tests/std_string (stderr) drd/tests/std_thread (stderr) drd/tests/std_thread2 (stderr) drd/tests/tc01_simple_race (stderr) drd/tests/tc02_simple_tls (stderr) drd/tests/tc03_re_excl (stderr) drd/tests/tc04_free_lock (stderr) drd/tests/tc05_simple_race (stderr) drd/tests/tc06_two_races (stderr) drd/tests/tc07_hbl1 (stderr) drd/tests/tc08_hbl2 (stderr) drd/tests/tc09_bad_unlock (stderr) drd/tests/tc16_byterace (stderr) drd/tests/tc17_sembar (stderr) drd/tests/tc18_semabuse (stderr) drd/tests/tc19_shadowmem (stderr) drd/tests/tc21_pthonce (stderr) drd/tests/tc23_bogus_condwait (stderr) drd/tests/tc24_nonzero_sem (stderr) drd/tests/thread_name (stderr) drd/tests/thread_name_xml (stderr) drd/tests/threaded-fork-vcs (stderr) drd/tests/threaded-fork (stderr) drd/tests/tls_threads (stderr) These all looked the same. drd thought a barrier was destroyed already. |