|
From: Julian S. <js...@ac...> - 2019-04-08 09:11:16
|
Greetings. 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. J |
|
From: Carl L. <ce...@us...> - 2019-04-08 17:25:59
|
On Mon, 2019-04-08 at 11:11 +0200, Julian Seward wrote: > Greetings. > > A first release candidate for 3.15.0 is available at > https://urldefense.proofpoint.com/v2/url?u=https-3A__sourceware.org_p > ub_valgrind_valgrind-2D3.15.0.RC1.tar.bz2&d=DwICAg&c=jf_iaSHvJObTbx- > siA1ZOg&r=RFEmMkZAk > -- > _wFGN5tkM_A&m=9hZ2UG1zq24navjF4vqXZNAqTv4POUs7ga6FtAyUoPI&s=QSm0l7sOp > efYvxnpN3ynVtY-em2qt2XMugYxHfjIMu0&e= > (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. Julian: I have run RC1 on Power 7, Power 8 LE, Power 8 BE and Power 9 and noted each system the same four post errors that I did not see last week when I tested patches to be committed. The errors are: cachegrind/tests/ann1 (post) cachegrind/tests/ann2 (post) callgrind/tests/ann1 (post) callgrind/tests/ann2 (post) I looked a little into the errors. I am not familiar with the tests. The diff files appear to be consistent across systems. Here is what I saw on the Power 8LE system. carll@genoa:~/valgrind-3.15.0.RC1/cachegrind/tests$ more ann1.post.diff --- ann1.post.exp 2019-04-08 03:20:27.000000000 -0500 +++ ann1.post.out 2019-04-08 11:59:21.571869076 -0500 @@ -31,19 +31,6 @@ 6,898 2 2 /build/glibc-OTsEL5/glibc-2.27/elf/dl-misc.c:_dl_name_matc h_p ------------------------------------------------------------------------------- - --- Auto-annotated source: a.c -------------------------------------------------------------------------------- - -Ir I1mr ILmr - - 2 0 0 int main(void) { - 1 1 1 int z = 0; -3,000,004 0 0 for (int i = 0; i < 1000000; i++) { -2,000,000 0 0 z += i; - . . . } - 6 0 0 return z % 256; - 2 0 0 } - -------------------------------------------------------------------------------- - The following files chosen for auto-annotation could not be found: ------------------------------------------------------------------------------- - /build/glibc-OTsEL5/glibc-2.27/elf/../sysdeps/x86_64/dl-machine.h @@ -53,9 +40,5 @@ /build/glibc-OTsEL5/glibc-2.27/elf/dl-tunables.h /build/glibc-OTsEL5/glibc-2.27/elf/do-rel.h /build/glibc-OTsEL5/glibc-2.27/string/../sysdeps/x86_64/strcmp.S - -------------------------------------------------------------------------------- - -Ir I1mr ILmr -------------------------------------------------------------------------------- - -5,000,015 1 1 events annotated + a.c *********************************************************************************** carll@genoa:~/valgrind-3.15.0.RC1/cachegrind/tests$ more ann2.post.diff --- ann2.post.exp 2019-04-08 03:20:27.000000000 -0500 +++ ann2.post.out 2019-04-08 11:59:22.447879150 -0500 @@ -28,28 +28,11 @@ 0 5,158 ( 0.13%) 25,408 ( 0.49%) /build/glibc-OTsEL5/glibc -2.27/string/../sysdeps/x86_64/strcmp.S:strcmp ------------------------------------------------------------------------------- - --- Auto-annotated source: a.c -------------------------------------------------------------------------------- - -Dw Dr Ir - -1 ( 0.01%) 0 2 ( 0.00%) int main(void) { -1 ( 0.01%) 0 1 ( 0.00%) int z = 0; -1 ( 0.01%) 2,000,001 (49.29%) 3,000,004 (57.36%) for (int i = 0; i < 100000 0; i++) { -0 2,000,000 (49.29%) 2,000,000 (38.24%) z += i; -. . . } -0 1 ( 0.00%) 6 ( 0.00%) return z % 256; -0 2 ( 0.00%) 2 ( 0.00%) } - -------------------------------------------------------------------------------- - The following files chosen for auto-annotation could not be found: ------------------------------------------------------------------------------- - /build/glibc-OTsEL5/glibc-2.27/elf/../sysdeps/x86_64/dl-machine.h /build/glibc-OTsEL5/glibc-2.27/elf/dl-lookup.c /build/glibc-OTsEL5/glibc-2.27/elf/dl-tunables.c /build/glibc-OTsEL5/glibc-2.27/string/../sysdeps/x86_64/strcmp.S - -------------------------------------------------------------------------------- - -Dw Dr Ir -------------------------------------------------------------------------------- - -3 ( 0.02%) 4,000,004 (98.57%) 5,000,015 (95.61%) events annotated + a.c ********************************************************************************************* carll@genoa:~/valgrind-3.15.0.RC1/callgrind/tests$ more ann1.post.diff --- ann1.post.exp 2019-04-08 03:20:27.000000000 -0500 +++ ann1.post.out 2019-04-08 11:59:26.451925196 -0500 @@ -32,19 +32,6 @@ 6,898 2 2 /build/glibc-OTsEL5/glibc-2.27/elf/dl-misc.c:_dl_name_matc h_p ------------------------------------------------------------------------------- - --- Auto-annotated source: ../../cachegrind/tests/ + a.c -------------------------------------------------------------------------------- - -Ir I1mr ILmr - - 2 0 0 int main(void) { - 1 1 1 int z = 0; -3,000,004 0 0 for (int i = 0; i < 1000000; i++) { -2,000,000 0 0 z += i; - . . . } - 6 0 0 return z % 256; - 2 0 0 } - -------------------------------------------------------------------------------- - The following files chosen for auto-annotation could not be found: ------------------------------------------------------------------------------- - /build/glibc-OTsEL5/glibc-2.27/elf/../sysdeps/x86_64/dl-machine.h @@ -54,9 +41,5 @@ /build/glibc-OTsEL5/glibc-2.27/elf/dl-tunables.h /build/glibc-OTsEL5/glibc-2.27/elf/do-rel.h /build/glibc-OTsEL5/glibc-2.27/string/../sysdeps/x86_64/strcmp.S - -------------------------------------------------------------------------------- - -Ir I1mr ILmr -------------------------------------------------------------------------------- - -5,000,015 1 1 events annotated + a.c *************************************************************************************** carll@genoa:~/valgrind-3.15.0.RC1/callgrind/tests$ more ann2.post.diff --- ann2.post.exp 2019-04-08 03:20:27.000000000 -0500 +++ ann2.post.out 2019-04-08 11:59:27.135933062 -0500 @@ -25,25 +25,8 @@ 4,543 (25.23%) 17,566 ( 0.43%) 47,993 ( 0.92%) /build/glibc-OTsEL5/glibc -2.27/elf/dl-lookup.c:do_lookup_x ------------------------------------------------------------------------------- - --- Auto-annotated source: ../../cachegrind/tests/ + a.c -------------------------------------------------------------------------------- - -Dw Dr Ir - -1 ( 0.01%) 0 2 ( 0.00%) int main(void) { -1 ( 0.01%) 0 1 ( 0.00%) int z = 0; -1 ( 0.01%) 2,000,001 (49.29%) 3,000,004 (57.36%) for (int i = 0; i < 100000 0; i++) { -0 2,000,000 (49.29%) 2,000,000 (38.24%) z += i; -. . . } -0 1 ( 0.00%) 6 ( 0.00%) return z % 256; -0 2 ( 0.00%) 2 ( 0.00%) } - -------------------------------------------------------------------------------- - The following files chosen for auto-annotation could not be found: ------------------------------------------------------------------------------- - /build/glibc-OTsEL5/glibc-2.27/elf/dl-lookup.c - -------------------------------------------------------------------------------- - -Dw Dr Ir -------------------------------------------------------------------------------- - -3 ( 0.02%) 4,000,004 (98.57%) 5,000,015 (95.61%) events annotated + a.c ****************************************************************************** I can't say for sure but I am guessing these will be architecture independent errors. Carl Love |
|
From: Mark W. <ma...@kl...> - 2019-04-09 12:08:29
|
On Mon, 2019-04-08 at 10:25 -0700, Carl Love wrote: > I have run RC1 on Power 7, Power 8 LE, Power 8 BE and Power 9 and > noted each system the same four post errors that I did not see last > week when I tested patches to be committed. The errors are: > > cachegrind/tests/ann1 (post) > cachegrind/tests/ann2 (post) > callgrind/tests/ann1 (post) > callgrind/tests/ann2 (post) > > I looked a little into the errors. I am not familiar with the tests. > > The diff files appear to be consistent across systems. It is indeed failing on other systems too. I filed the following bug, with proposed fix: https://bugs.kde.org/show_bug.cgi?id=406352 > I can't say for sure but I am guessing these will be architecture > independent errors. Cheers, Mark |
|
From: Mark W. <ma...@kl...> - 2019-04-08 19:47:44
Attachments:
libstdc++.supp.patch
|
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. |
|
From: Mark W. <ma...@kl...> - 2019-04-09 07:02:34
|
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. For users are binary rpms for fedora and centos in koji and on copr if people find that easier to use for testing: https://koji.fedoraproject.org/koji/buildinfo?buildID=1246875 https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.15.0/ For developers the build.logs do contain the make regtest diffs for any failing tests. Cheers, Mark |
|
From: Roger L. <ro...@at...> - 2019-04-09 13:43:31
|
Hello, I have made RC1 available on the Snap package store in the "edge" channel, so it can be tested on systems that have snap support with "snap install --classic --edge valgrind". I have also run the tests on Ubuntu 19.04 amd64 with gcc 8.3.0, binutils 2.32, glibc-2.29, linux 5.0.0 and gdb 8.2.90.20190311. == 709 tests, 4 stderr failures, 0 stdout failures, 2 stderrB failures, 18 stdoutB failures, 4 post failures == gdbserver_tests/hginfo (stdoutB) gdbserver_tests/hgtls (stdoutB) gdbserver_tests/mcblocklistsearch (stderrB) gdbserver_tests/mcbreak (stdoutB) gdbserver_tests/mcclean_after_fork (stdoutB) gdbserver_tests/mcleak (stdoutB) gdbserver_tests/mcmain_pic (stdoutB) gdbserver_tests/mcsignopass (stdoutB) gdbserver_tests/mcsigpass (stdoutB) gdbserver_tests/mcvabits (stdoutB) gdbserver_tests/mcwatchpoints (stdoutB) gdbserver_tests/mssnapshot (stdoutB) gdbserver_tests/nlcontrolc (stdoutB) gdbserver_tests/nlgone_abrt (stdoutB) gdbserver_tests/nlgone_exit (stdoutB) gdbserver_tests/nlgone_return (stdoutB) gdbserver_tests/nlpasssigalrm (stdoutB) gdbserver_tests/nlsigvgdb (stdoutB) gdbserver_tests/nlvgdbsigqueue (stdoutB) These all fail due to a minor change in the gdb output format as described on https://bugs.kde.org/show_bug.cgi?id=406357 gdbserver_tests/mcinfcallWSRU (stderr) gdbserver_tests/mcinfcallWSRU (stderrB) This test fails to complete. I killed it after about 3 hours. The same test from 3.14.0 completed on this setup. none/tests/amd64-linux/map_32bits (stderr) Diff is: --- map_32bits.stderr.exp 2019-04-08 09:20:28.000000000 +0100 +++ map_32bits.stderr.out 2019-04-09 14:29:28.408169636 +0100 @@ -1,3 +1 @@ -first mmap : 0x........ -last mmap ok: 0x........ -retry mmap ok: 0x........ +first mmap: Cannot allocate memory exp-sgcheck/tests/stackerr (stderr) The __v*printf_internal part can be filtered, but I don't know what the other part of the diff means: --- stackerr.stderr.exp-glibc28-amd64 2019-04-08 09:20:27.000000000 +0100 +++ stackerr.stderr.out 2019-04-09 14:25:34.679919272 +0100 @@ -17,11 +17,11 @@ Invalid write of size 1 at 0x........: _IO_default_xsputn (in /...libc...) - by 0x........: ... - by 0x........: ... + by 0x........: __vfprintf_internal (vfprintf-internal.c:1644) + by 0x........: __vsprintf_internal (iovsprintf.c:95) Address 0x........ expected vs actual: Expected: stack array "buf" of size 8 in frame 4 back from here - Actual: unknown + Actual: stack array "beforebuf" of size 8 in frame 4 back from here Actual: is 0 after Expected memcheck/tests/overlap (stderr) cachegrind/tests/ann1 (post) cachegrind/tests/ann2 (post) callgrind/tests/ann1 (post) callgrind/tests/ann2 (post) These results are the same as reported by Carl and Mark: Cheers, Roger On Mon, 8 Apr 2019 at 10:11, Julian Seward <js...@ac...> wrote: > > > Greetings. > > 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. > > J > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Mark W. <ma...@kl...> - 2019-04-10 12:11:32
|
On Tue, 2019-04-09 at 09:02 +0200, Mark Wielaard wrote: > 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. > > For users are binary rpms for fedora and centos in koji and on copr > if > people find that easier to use for testing: > > https://koji.fedoraproject.org/koji/buildinfo?buildID=1246875 > https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.15.0/ > > For developers the build.logs do contain the make regtest diffs for > any > failing tests. I did new builds with the one extra commit and a couple of bug fixes: https://koji.fedoraproject.org/koji/buildinfo?buildID=1247329 https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.15.0/build/881204/ This includes the following extra fixes: valgrind commit b2d2da64b0de1c4d657b63187967b68606e84711 GET_STARTREGS for s390: fix register constraint KDE#406352 RC1 fails cachegrind/callgrind ann tests because of missing a.c KDE#406360 memcheck/tests/libstdc++.supp needs more supression variants KDE#406354 dhat is broken on x86 (32bit) KDE#406355 mcsignopass and mcsigpass fails due to a difference in gdb output KDE#406357 RC1 fails gdbserver_tests because of gdb output change I hand tested them all (because I made the mistake of only running the nonexp-regtest (which doesn't include gdbserver_tests) and messed up the data on the a.c file, which generates a warning, but shows the fix itself is good. May I push these fixes to git? Should they go on the master branch, or is there a 3.15.0 branch already? Thanks, Mark |
|
From: Julian S. <js...@ac...> - 2019-04-10 12:40:23
|
Thanks for the testing and for chasing these failures. OK for all: > KDE#406352 > RC1 fails cachegrind/callgrind ann tests because of missing a.c OK (incl comment 1 fix) > KDE#406360 > memcheck/tests/libstdc++.supp needs more supression variants OK (not optimal, but I don't know what else we can do) > KDE#406354 > dhat is broken on x86 (32bit) OK (this means you are the first person ever to run dhat on x86-linux :) > KDE#406355 > mcsignopass and mcsigpass fails due to a difference in gdb output OK (if you + PhilippeW think it's fine, then fine) > KDE#406357 > RC1 fails gdbserver_tests because of gdb output change OK (same comment as above) J |
|
From: Julian S. <js...@ac...> - 2019-04-11 08:56:27
|
Thank you to everybody who tested RC1, sent reports and bug fixes. RC2 is now available at https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC2.tar.bz2 (md5 = 672e065ec63ae127ee4439cd296fb142). It contains fixes for five minor regression test failures, but nothing major. Unless any serious failures are reported in RC2, this is very likely to morph into the final 3.15.0 release. J > On 08/04/2019 11:11, 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. > > J |
|
From: Roger L. <ro...@at...> - 2019-04-11 12:17:33
|
Hello,
I tested RC2 on Ubuntu 19.04 amd64 with gcc 8.3.0, binutils 2.32,
glibc-2.29, linux 5.0.0 and gdb 8.2.90.20190311.
I get the same problems as before, less the ones that have been fixed.
If I retest with LTO enabled I get a new error:
helgrind/tests/tc09_bad_unlock (stderr)
--- tc09_bad_unlock.stderr.exp 2019-04-11 08:48:32.000000000 +0100
+++ tc09_bad_unlock.stderr.out 2019-04-11 11:12:21.345129726 +0100
@@ -117,7 +117,6 @@
by 0x........: nearly_main (tc09_bad_unlock.c:31)
by 0x........: main (tc09_bad_unlock.c:49)
Address 0x........ is on thread #x's stack
- in frame #x, created by nearly_main (tc09_bad_unlock.c:16)
Regards,
Roger
On Thu, 11 Apr 2019 at 09:56, Julian Seward <js...@ac...> wrote:
>
>
> Thank you to everybody who tested RC1, sent reports and bug fixes.
>
> RC2 is now available at
> https://sourceware.org/pub/valgrind/valgrind-3.15.0.RC2.tar.bz2
> (md5 = 672e065ec63ae127ee4439cd296fb142). It contains fixes for
> five minor regression test failures, but nothing major.
>
> Unless any serious failures are reported in RC2, this is very likely
> to morph into the final 3.15.0 release.
>
> J
>
> > On 08/04/2019 11:11, 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.
> >
> > J
>
>
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
|
|
From: Petar J. <mip...@gm...> - 2019-04-11 16:34:03
|
All the tests are passing for MIPS32 and MIPS64. Regards, Petar |
|
From: Rhys K. <rhy...@gm...> - 2019-04-13 14:11:08
|
I'm not seeing any regressions in 3.15.0 on Git for the currently-supported macOS versions. Regards, Rhys On Fri, 12 Apr 2019 at 02:34, Petar Jovanovic <mip...@gm...> wrote: > All the tests are passing for MIPS32 and MIPS64. > > Regards, > Petar > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |