|
From: Julian S. <js...@ac...> - 2018-10-03 15:54:10
|
Greetings. Per the subject line, valgrind-3.14.0.RC2 is available for testing, at: ftp://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 https://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 (md5 = e92f8816973396edd6d0cbcd820ccca0) Please give it a try on systems, and in configurations, which are important for you, and report any failures (and successes!) here. I propose to make the final 3.14.0 release on Tuesday 9 October if no serious breakage is reported. As ever, the NEWS file in the tarball lists the new features and fixed bugs in this release. J |
|
From: Carl L. <ce...@us...> - 2018-10-04 20:44:50
|
Julian:
I tested RC2 on Power 7, 8 and 9. In summary, valgrind 3.14.RC2 is
much better then the 3.13 release. We generally see fewer errors being
reported in general. There were no new errors that are of a concern.
The RC2 release looks good to me.
Below is a detailed reporting of the results if you are interested.
Carl Love
======================================================================
The Power 7 testing comparison between 3.13 and 3.14.RC2
The 3.13 release reported:
== 648 tests, 5 stderr failures, 5 stdout failures, 0 stderrB failures, 1 stdoutB failure, 1 post failure ==
gdbserver_tests/hgtls (stdoutB)
memcheck/tests/bug340392 (stderr)
memcheck/tests/leak_cpp_interior (stderr)
massif/tests/mmapunmap (post)
none/tests/linux/clonev (stdout)
none/tests/linux/clonev (stderr)
none/tests/ppc32/jm-vmx (stdout)
none/tests/ppc32/power5+_round (stdout)
none/tests/ppc32/testVMX (stdout)
none/tests/ppc64/jm-vmx (stdout)
drd/tests/std_thread (stderr)
drd/tests/std_thread2 (stderr)
The 3.14.0.RC2 release reports:
== 657 tests, 10 stderr failures, 5 stdout failures, 0 stderrB failures, 1 stdoutB failure, 0 post failures ==
gdbserver_tests/hgtls (stdoutB)
memcheck/tests/bug340392 (stderr)
memcheck/tests/leak_cpp_interior (stderr)
none/tests/linux/clonev (stdout)
none/tests/linux/clonev (stderr)
none/tests/ppc32/jm-vmx (stdout)
none/tests/ppc32/power5+_round (stdout)
none/tests/ppc32/testVMX (stdout)
none/tests/ppc64/jm-vmx (stdout)
drd/tests/annotate_ignore_read (stderr) << not reported in 3.13, reports libstdc++.so.6
version `CXXABI_1.3.11' not found
drd/tests/annotate_order_1 (stderr) << not reported in 3.13, ditto on error
drd/tests/annotate_order_2 (stderr) << not reported in 3.13, ditto on error
drd/tests/annotate_order_3 (stderr) << not reported in 3.13, ditto on error
drd/tests/annotate_spinlock (stderr) << not reported in 3.13, ditto on error
drd/tests/std_thread (stderr)
drd/tests/std_thread2 (stderr)
The additional errors appear to be from a version mismatch. Not
concerned about the "new" errors. I think valgrind-3.14.0.RC2 looks
good here.
----------------------------------------------------------------
The Power 8 testing comparison between 3.13 and 3.14.RC2
The 3.13 release reported:
== 618 tests, 9 stderr failures, 3 stdout failures, 0 stderrB failures, 3 stdoutB fagdbserver_tests/hgtls (stdoutB)
gdbserver_tests/nlgone_abrt (stdoutB)
gdbserver_tests/nlpasssigalrm (stdoutB)
memcheck/tests/bug340392 (stderr)
memcheck/tests/leak_cpp_interior (stderr)
memcheck/tests/linux/rfcomm (stderr)
memcheck/tests/ppc64/power_ISA2_05 (stderr)
memcheck/tests/ppc64/power_ISA2_07 (stderr)
memcheck/tests/strchr (stderr)
massif/tests/deep-D (post)
massif/tests/new-cpp (post)
massif/tests/overloaded-new (post)
none/tests/fdleak_ipv4 (stderr)
none/tests/ppc64/jm-vmx (stdout)
none/tests/ppc64/test_isa_2_06_part1 (stdout)
none/tests/ppc64/test_isa_2_06_part3 (stdout)
drd/tests/std_thread (stderr)
drd/tests/std_thread2 (stderr)ilures, 3 post failures ==
The 3.14.0.RC2 release reports:
== 628 tests, 5 stderr failures, 0 stdout failures, 0 stderrB failures,
2 stdoutB failures, 2 post failures ==
gdbserver_tests/nlgone_abrt (stdoutB)
gdbserver_tests/nlpasssigalrm (stdoutB)
memcheck/tests/bug340392 (stderr)
memcheck/tests/leak_cpp_interior (stderr)
memcheck/tests/linux/rfcomm (stderr)
memcheck/tests/strchr (stderr)
massif/tests/new-cpp (post)
massif/tests/overloaded-new (post)
none/tests/fdleak_ipv4 (stderr)
All of these failures were in the 3.13 release, i.e. no new failures.
Looks good on Power 8.
--------------------------------------------------------------------
The Power 9 testing comparison between 3.13 and 3.14.RC2
On Power 9
The 3.13.0 release will compile but "make regtest" fails to compile
memcheck/tests/linux/stack_changes.c. I "commented out" the test and
was able to get make regtest to run. It reports:
== 619 tests, 13 stderr failures, 4 stdout failures, 2 stderrB failures, 5 stdoutB failures, 3 post failures ==
gdbserver_tests/hgtls (stdoutB)
gdbserver_tests/mcblocklistsearch (stderrB)
gdbserver_tests/mcinfcallWSRU (stderrB)
gdbserver_tests/mcmain_pic (stderr)
gdbserver_tests/nlcontrolc (stdoutB)
gdbserver_tests/nlgone_abrt (stdoutB)
gdbserver_tests/nlpasssigalrm (stdoutB)
gdbserver_tests/nlvgdbsigqueue (stdoutB)
memcheck/tests/bug340392 (stderr)
memcheck/tests/file_locking (stderr)
memcheck/tests/leak_cpp_interior (stderr)
memcheck/tests/linux/rfcomm (stderr)
memcheck/tests/linux/stack_changes (stdout)
memcheck/tests/ppc64/power_ISA2_05 (stderr)
memcheck/tests/ppc64/power_ISA2_07 (stderr)
memcheck/tests/sigkill (stderr)
memcheck/tests/str_tester (stderr)
memcheck/tests/threadname_xml (stderr)
memcheck/tests/vcpu_fnfns (stdout)
memcheck/tests/vcpu_fnfns (stderr)
massif/tests/deep-D (post)
massif/tests/new-cpp (post)
massif/tests/overloaded-new (post)
none/tests/ppc64/test_isa_3_0_altivec (stdout)
none/tests/ppc64/test_isa_3_0_other (stdout)
none/tests/rlimit_nofile (stderr)
none/tests/scripts/shell (stderr)
3.14.0.RC2 builds and runs "make regtest" cleanly, it reports:
== 629 tests, 4 stderr failures, 1 stdout failure, 0 stderrB failures, 1 stdoutB failure, 2 post failures ==
gdbserver_tests/nlcontrolc (stdoutB) << not reported on Power8, also fails on Power9 3.13
memcheck/tests/bug340392 (stderr)
memcheck/tests/leak_cpp_interior (stderr)
memcheck/tests/linux/rfcomm (stderr)
memcheck/tests/vbit-test/vbit-test (stderr) << not reported on Power 8, also fails on Power9 3.13
memcheck/tests/vcpu_fnfns (stdout) << not reported on Power 8, also fails on Power9 3.13
massif/tests/new-cpp (post)
massif/tests/overloaded-new (post)
Clearly an improvement over 3.13.0. No "new" errors. 3.14.0.RC2 looks good on this platform.
|
|
From: Mark W. <ma...@kl...> - 2018-10-04 20:55:05
|
On Wed, Oct 03, 2018 at 05:53:57PM +0200, Julian Seward wrote: > Per the subject line, valgrind-3.14.0.RC2 is available for testing, at: > > ftp://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 > https://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 > (md5 = e92f8816973396edd6d0cbcd820ccca0) > > Please give it a try on systems, and in configurations, which are important > for you, and report any failures (and successes!) here. I propose to make the > final 3.14.0 release on Tuesday 9 October if no serious breakage is reported. For Fedora users there are packages here: https://koji.fedoraproject.org/koji/buildinfo?buildID=1149947 And for CentOS (and Fedora 28) users there are packages here: https://copr.fedorainfracloud.org/coprs/mjw/valgrind-3.14.0/ Cheers, Mark |
|
From: Jonathan L. <jon...@gm...> - 2018-10-04 21:41:57
|
Hi,
What is the intended support status of macOS 10.13.x High Sierra? What
about macOS 10.14 Mojave?
Some time ago, I downloaded an interim version of Valgrind from Git (git
pull) and amongst other files there was a darwin17.supp file . That seems
to be missing from the 3.14.0.RC2 tar file. Consequently, although it
configured OK on macOS 10.13.6, it failed to build at a very early stage.
I've not yet tried the build on Mojave, but that would presumably fail
because of a missing darwin18.supp file.
The commit I have that has worked on macOS 10.13.x was:
commit 92d6a538862a784156ee5fff297eb7daba733127 (HEAD -> master,
origin/master, origin/HEAD)
Author: Rhys Kidd <rhy...@gm...>
Date: Sun Jun 3 12:40:13 2018 -0400
Fix missing kevent_qos syscall (macOS 10.11). bz#383723
The version built on High Sierra ran on Mojave, but had a new set of
warnings — extensive ones. I assume these should simply be built into a
suppressions file for Mojave, in the absence of any better solution.
On Wed, Oct 3, 2018 at 8:54 AM Julian Seward <js...@ac...> wrote:
>
> Greetings.
>
> Per the subject line, valgrind-3.14.0.RC2 is available for testing, at:
>
> ftp://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2
> https://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2
> (md5 = e92f8816973396edd6d0cbcd820ccca0)
>
> Please give it a try on systems, and in configurations, which are important
> for you, and report any failures (and successes!) here. I propose to make
> the
> final 3.14.0 release on Tuesday 9 October if no serious breakage is
> reported.
>
> As ever, the NEWS file in the tarball lists the new features and fixed
> bugs in
> this release.
>
> J
>
>
> _______________________________________________
> Valgrind-developers mailing list
> Val...@li...
> https://lists.sourceforge.net/lists/listinfo/valgrind-developers
>
--
Jonathan Leffler <jon...@gm...> #include <disclaimer.h>
Guardian of DBD::Informix - v2015.1101 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."
|
|
From: Philippe W. <phi...@sk...> - 2018-10-05 05:36:04
|
If you try to build the RC2 but from the git repository, does that work better ? If the same git version builds/runs ok, then it is probably just a tar ball packaging problem ... Philippe On Thu, 2018-10-04 at 14:41 -0700, Jonathan Leffler wrote: > Hi, > > What is the intended support status of macOS 10.13.x High Sierra? What about macOS 10.14 Mojave? > > Some time ago, I downloaded an interim version of Valgrind from Git (git pull) and amongst other files there was a darwin17.supp file . That seems to be missing from the 3.14.0.RC2 tar file. Consequently, although it configured OK on macOS 10.13.6, it failed to build at a very early stage. I've not yet tried the build on Mojave, but that would presumably fail because of a missing darwin18.supp file. > > The commit I have that has worked on macOS 10.13.x was: > > commit 92d6a538862a784156ee5fff297eb7daba733127 (HEAD -> master, origin/master, origin/HEAD) > Author: Rhys Kidd <rhy...@gm...> > Date: Sun Jun 3 12:40:13 2018 -0400 > > Fix missing kevent_qos syscall (macOS 10.11). bz#383723 > > The version built on High Sierra ran on Mojave, but had a new set of warnings — extensive ones. I assume these should simply be built into a suppressions file for Mojave, in the absence of any better solution. > > > On Wed, Oct 3, 2018 at 8:54 AM Julian Seward <js...@ac...> wrote: > > Greetings. > > > > Per the subject line, valgrind-3.14.0.RC2 is available for testing, at: > > > > ftp://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 > > https://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 > > (md5 = e92f8816973396edd6d0cbcd820ccca0) > > > > Please give it a try on systems, and in configurations, which are important > > for you, and report any failures (and successes!) here. I propose to make the > > final 3.14.0 release on Tuesday 9 October if no serious breakage is reported. > > > > As ever, the NEWS file in the tarball lists the new features and fixed bugs in > > this release. > > > > J > > > > > > _______________________________________________ > > Valgrind-developers mailing list > > Val...@li... > > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > > > > -- > Jonathan Leffler <jon...@gm...> #include <disclaimer.h> > Guardian of DBD::Informix - v2015.1101 - http://dbi.perl.org > "Blessed are we who can laugh at ourselves, for we shall never cease to be amused." > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Roger L. <rog...@ce...> - 2018-10-05 23:30:31
|
Hello, I built and tested on a Mac with OS X version 10.13.6. I have the same problem with the tarball, but the git checkout built just fine. make regtest produced: == 643 tests, 328 stderr failures, 83 stdout failures, 1 stderrB failure, 1 stdoutB failure, 31 post failures == Which is a lot of errors. But I may have done something wrong (build and test was: ./autogen.sh ; ./configure ; make -j8 ; make regtest) Cheers, Roger On Fri, 5 Oct 2018 at 06:36, Philippe Waroquiers < phi...@sk...> wrote: > If you try to build the RC2 but from the git repository, > does that work better ? > > If the same git version builds/runs ok, then it is probably > just a tar ball packaging problem ... > > Philippe > > > On Thu, 2018-10-04 at 14:41 -0700, Jonathan Leffler wrote: > > Hi, > > > > What is the intended support status of macOS 10.13.x High Sierra? What > about macOS 10.14 Mojave? > > > > Some time ago, I downloaded an interim version of Valgrind from Git (git > pull) and amongst other files there was a darwin17.supp file . That seems > to be missing from the 3.14.0.RC2 tar file. Consequently, although it > configured OK on macOS 10.13.6, it failed to build at a very early stage. > I've not yet tried the build on Mojave, but that would presumably fail > because of a missing darwin18.supp file. > > > > The commit I have that has worked on macOS 10.13.x was: > > > > commit 92d6a538862a784156ee5fff297eb7daba733127 (HEAD -> master, > origin/master, origin/HEAD) > > Author: Rhys Kidd <rhy...@gm...> > > Date: Sun Jun 3 12:40:13 2018 -0400 > > > > Fix missing kevent_qos syscall (macOS 10.11). bz#383723 > > > > The version built on High Sierra ran on Mojave, but had a new set of > warnings — extensive ones. I assume these should simply be built into a > suppressions file for Mojave, in the absence of any better solution. > > > > > > On Wed, Oct 3, 2018 at 8:54 AM Julian Seward <js...@ac...> wrote: > > > Greetings. > > > > > > Per the subject line, valgrind-3.14.0.RC2 is available for testing, at: > > > > > > ftp://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 > > > https://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 > > > (md5 = e92f8816973396edd6d0cbcd820ccca0) > > > > > > Please give it a try on systems, and in configurations, which are > important > > > for you, and report any failures (and successes!) here. I propose to > make the > > > final 3.14.0 release on Tuesday 9 October if no serious breakage is > reported. > > > > > > As ever, the NEWS file in the tarball lists the new features and fixed > bugs in > > > this release. > > > > > > J > > > > > > > > > _______________________________________________ > > > Valgrind-developers mailing list > > > Val...@li... > > > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > > > > > > > > -- > > Jonathan Leffler <jon...@gm...> #include <disclaimer.h> > > Guardian of DBD::Informix - v2015.1101 - http://dbi.perl.org > > "Blessed are we who can laugh at ourselves, for we shall never cease to > be amused." > > _______________________________________________ > > Valgrind-developers mailing list > > Val...@li... > > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Paul F. <pj...@wa...> - 2018-10-06 11:29:42
|
> On 6 Oct 2018, at 01:05, Roger Light <rog...@ce...> wrote: > > Hello, > > I built and tested on a Mac with OS X version 10.13.6. I have the same problem with the tarball, but the git checkout built just fine. > > make regtest produced: > > == 643 tests, 328 stderr failures, 83 stdout failures, 1 stderrB failure, 1 stdoutB failure, 31 post failures == > > Which is a lot of errors. But I may have done something wrong (build and test was: ./autogen.sh ; ./configure ; make -j8 ; make regtest) > > Cheers, > > Roger Hi Similar results here macOS 10.13.6 == 643 tests, 328 stderr failures, 84 stdout failures, 1 stderrB failure, 1 stdoutB failure, 31 post failures == Solaris 11.3 == 747 tests, 13 stderr failures, 3 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == Fedora 24 == 766 tests, 2 stderr failures, 0 stdout failures, 0 stderrB failures, 0 stdoutB failures, 0 post failures == A+ Paul |
|
From: Rhys K. <rhy...@gm...> - 2018-10-05 23:35:21
|
On Fri, 5 Oct 2018 at 19:31, Roger Light <rog...@ce...> wrote: > Hello, > > I built and tested on a Mac with OS X version 10.13.6. I have the same > problem with the tarball, but the git checkout built just fine. > Thanks for this report. I'll look at what needs to be done to fix the tarball for the next RC. > make regtest produced: > > == 643 tests, 328 stderr failures, 83 stdout failures, 1 stderrB failure, > 1 stdoutB failure, 31 post failures == > > Which is a lot of errors. But I may have done something wrong (build and > test was: ./autogen.sh ; ./configure ; make -j8 ; make regtest) > Unfortunately, that level of test suite errors is to be expected with valgrind on modern macOS. (Our CI runners report about the same). With only one active macOS-focused valgrind developer, and a constantly moving target of the Apple darwin kernel interfaces, the support isn't great. If improved valgrind macOS support is of interest to you or your employer, I'd be interested in talking further about ways additional time could be invested to improve the current unideal situation. > > Cheers, > > Roger > > On Fri, 5 Oct 2018 at 06:36, Philippe Waroquiers < > phi...@sk...> wrote: > >> If you try to build the RC2 but from the git repository, >> does that work better ? >> >> If the same git version builds/runs ok, then it is probably >> just a tar ball packaging problem ... >> >> Philippe >> >> >> On Thu, 2018-10-04 at 14:41 -0700, Jonathan Leffler wrote: >> > Hi, >> > >> > What is the intended support status of macOS 10.13.x High Sierra? What >> about macOS 10.14 Mojave? >> > >> > Some time ago, I downloaded an interim version of Valgrind from Git >> (git pull) and amongst other files there was a darwin17.supp file . That >> seems to be missing from the 3.14.0.RC2 tar file. Consequently, although >> it configured OK on macOS 10.13.6, it failed to build at a very >> early stage. I've not yet tried the build on Mojave, but that would >> presumably fail because of a missing darwin18.supp file. >> > >> > The commit I have that has worked on macOS 10.13.x was: >> > >> > commit 92d6a538862a784156ee5fff297eb7daba733127 (HEAD -> master, >> origin/master, origin/HEAD) >> > Author: Rhys Kidd <rhy...@gm...> >> > Date: Sun Jun 3 12:40:13 2018 -0400 >> > >> > Fix missing kevent_qos syscall (macOS 10.11). bz#383723 >> > >> > The version built on High Sierra ran on Mojave, but had a new set of >> warnings — extensive ones. I assume these should simply be built into a >> suppressions file for Mojave, in the absence of any better solution. >> > >> > >> > On Wed, Oct 3, 2018 at 8:54 AM Julian Seward <js...@ac...> wrote: >> > > Greetings. >> > > >> > > Per the subject line, valgrind-3.14.0.RC2 is available for testing, >> at: >> > > >> > > ftp://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 >> > > https://sourceware.org/pub/valgrind/valgrind-3.14.0.RC2.tar.bz2 >> > > (md5 = e92f8816973396edd6d0cbcd820ccca0) >> > > >> > > Please give it a try on systems, and in configurations, which are >> important >> > > for you, and report any failures (and successes!) here. I propose to >> make the >> > > final 3.14.0 release on Tuesday 9 October if no serious breakage is >> reported. >> > > >> > > As ever, the NEWS file in the tarball lists the new features and >> fixed bugs in >> > > this release. >> > > >> > > J >> > > >> > > >> > > _______________________________________________ >> > > Valgrind-developers mailing list >> > > Val...@li... >> > > https://lists.sourceforge.net/lists/listinfo/valgrind-developers >> > > >> > >> > >> > -- >> > Jonathan Leffler <jon...@gm...> #include <disclaimer.h> >> > Guardian of DBD::Informix - v2015.1101 - http://dbi.perl.org >> > "Blessed are we who can laugh at ourselves, for we shall never cease to >> be amused." >> > _______________________________________________ >> > Valgrind-developers mailing list >> > Val...@li... >> > https://lists.sourceforge.net/lists/listinfo/valgrind-developers >> >> >> _______________________________________________ >> Valgrind-developers mailing list >> Val...@li... >> https://lists.sourceforge.net/lists/listinfo/valgrind-developers >> > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > |
|
From: Roger L. <rog...@ce...> - 2018-10-06 07:39:14
|
On Sat, 6 Oct 2018 at 00:35, Rhys Kidd <rhy...@gm...> wrote: > If improved valgrind macOS support is of interest to you or your employer, > I'd be interested in talking further about ways additional time could be > invested to improve the current unideal situation. > I confess this was the first time I've used valgrind on a mac - I only have it for bugfixing purposes, my development is done elsewhere. Having said that, let me know what's involved and I might be able to spend some time on it occasionally. Cheers, Roger |
|
From: Rhys K. <rhy...@gm...> - 2018-10-08 01:50:25
|
On Sat, 6 Oct 2018 at 03:39, Roger Light <rog...@ce...> wrote: > On Sat, 6 Oct 2018 at 00:35, Rhys Kidd <rhy...@gm...> wrote: > >> If improved valgrind macOS support is of interest to you or your >> employer, I'd be interested in talking further about ways additional time >> could be invested to improve the current unideal situation. >> > > I confess this was the first time I've used valgrind on a mac - I only > have it for bugfixing purposes, my development is done elsewhere. > > Having said that, let me know what's involved and I might be able to spend > some time on it occasionally. > > Cheers, > > Roger > > The fix for this has been identified [0], and should be in an RC3 or final (depending upon which Julian Seward decides to do). [0] https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=353a3587bb0e2757411f9138f5e936728ed6cc4f |
|
From: Petar J. <mip...@gm...> - 2018-10-06 12:53:06
|
On Wed, Oct 3, 2018 at 5:54 PM Julian Seward <js...@ac...> wrote: > > Please give it a try on systems, and in configurations, which are important > for you, and report any failures (and successes!) here. All fine on various MIPS configurations. Regards, Petar |