You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
1
(1) |
2
|
3
(4) |
4
(3) |
5
(3) |
6
(3) |
|
7
|
8
(2) |
9
(3) |
10
(1) |
11
|
12
|
13
|
|
14
|
15
|
16
(3) |
17
|
18
(8) |
19
(2) |
20
(5) |
|
21
|
22
|
23
|
24
|
25
|
26
|
27
(2) |
|
28
(2) |
29
|
30
|
31
|
|
|
|
|
From: Julian S. <se...@so...> - 2018-10-09 11:53:32
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=3a3000290b4af0e8ef9880293c54659a6819ba78 commit 3a3000290b4af0e8ef9880293c54659a6819ba78 Author: Julian Seward <js...@ac...> Date: Tue Oct 9 13:52:05 2018 +0200 --> 3.14.0 final Diff: --- NEWS | 1 + configure.ac | 2 +- docs/xml/vg-entities.xml | 2 +- 3 files changed, 3 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 6e0c82b..91e572e 100644 --- a/NEWS +++ b/NEWS @@ -187,6 +187,7 @@ n-i-bz Signal delivery for x86-linux: ensure that the stack pointer is (3.14.0.RC1: 30 September 2018, git c2aeea2d28acb0639bcc8cc1e4ab115067db1eae) (3.14.0.RC2: 3 October 2018, git 3e214c4858a6fdd5697e767543a0c19e30505582) +(3.14.0: 9 October 2018, git 353a3587bb0e2757411f9138f5e936728ed6cc4f) diff --git a/configure.ac b/configure.ac index 98d22b6..c18ae5f 100644 --- a/configure.ac +++ b/configure.ac @@ -8,7 +8,7 @@ ##------------------------------------------------------------## # Process this file with autoconf to produce a configure script. -AC_INIT([Valgrind],[3.14.0.RC2],[val...@li...]) +AC_INIT([Valgrind],[3.14.0],[val...@li...]) AC_CONFIG_SRCDIR(coregrind/m_main.c) AC_CONFIG_HEADERS([config.h]) AM_INIT_AUTOMAKE([foreign subdir-objects]) diff --git a/docs/xml/vg-entities.xml b/docs/xml/vg-entities.xml index 5d01d95..6151c35 100644 --- a/docs/xml/vg-entities.xml +++ b/docs/xml/vg-entities.xml @@ -7,7 +7,7 @@ <!-- valgrind release + version stuff --> <!ENTITY rel-type "Release"> <!ENTITY rel-version "3.14.0"> -<!ENTITY rel-date "4 October 2018"> +<!ENTITY rel-date "9 October 2018"> <!-- where the docs are installed --> <!ENTITY vg-docs-path "$INSTALL/share/doc/valgrind/html/index.html"> |
|
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: Rhys K. <rhy...@so...> - 2018-10-08 01:44:50
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=353a3587bb0e2757411f9138f5e936728ed6cc4f commit 353a3587bb0e2757411f9138f5e936728ed6cc4f Author: Rhys Kidd <rhy...@gm...> Date: Sun Oct 7 21:26:35 2018 -0400 Fix macOS 10.13 building from tarball Fixes: 1ce04c3 ("Preliminary support for Darwin 17.x (macOS 10.13)") Diff: --- Makefile.am | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Makefile.am b/Makefile.am index fdce3cf..154f68f 100644 --- a/Makefile.am +++ b/Makefile.am @@ -47,7 +47,7 @@ SUPP_FILES = \ darwin9.supp darwin9-drd.supp \ darwin10.supp darwin10-drd.supp \ darwin11.supp darwin12.supp darwin13.supp darwin14.supp darwin15.supp \ - darwin16.supp \ + darwin16.supp darwin17.supp \ bionic.supp \ solaris11.supp solaris12.supp DEFAULT_SUPP_FILES = @DEFAULT_SUPP@ |
|
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 |
|
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: 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-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-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: 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: 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: 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: 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: 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: Julian S. <se...@so...> - 2018-10-03 13:38:05
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=d2af42d826d65f3a6722a33309e721264846efd3 commit d2af42d826d65f3a6722a33309e721264846efd3 Author: Julian Seward <js...@ac...> Date: Wed Oct 3 15:37:06 2018 +0200 --> 3.14.0.RC2 Diff: --- NEWS | 8 ++++++-- configure.ac | 2 +- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index 02eb2c6..6e0c82b 100644 --- a/NEWS +++ b/NEWS @@ -1,4 +1,4 @@ -Release 3.14.0 (4 October 2018) +Release 3.14.0 (9 October 2018) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.14.0 is a feature release with many improvements and the usual collection of @@ -181,8 +181,12 @@ n-i-bz Add support for the Linux BLKFLSBUF ioctl n-i-bz Add support for the Linux BLKREPORTZONE and BLKRESETZONE ioctls n-i-bz Fix possible stack trashing by semctl syscall wrapping n-i-bz Add support for the Linux membarrier() system call +n-i-bz x86 front end: recognise and handle UD2 correctly +n-i-bz Signal delivery for x86-linux: ensure that the stack pointer is + correctly aligned before entering the handler. -(3.14.0.RC1: 30 September 2018, git c2aeea2d28acb0639bcc8cc1e4ab115067db1eae) +(3.14.0.RC1: 30 September 2018, git c2aeea2d28acb0639bcc8cc1e4ab115067db1eae) +(3.14.0.RC2: 3 October 2018, git 3e214c4858a6fdd5697e767543a0c19e30505582) diff --git a/configure.ac b/configure.ac index 1603079..98d22b6 100644 --- a/configure.ac +++ b/configure.ac @@ -8,7 +8,7 @@ ##------------------------------------------------------------## # Process this file with autoconf to produce a configure script. -AC_INIT([Valgrind],[3.14.0.RC1],[val...@li...]) +AC_INIT([Valgrind],[3.14.0.RC2],[val...@li...]) AC_CONFIG_SRCDIR(coregrind/m_main.c) AC_CONFIG_HEADERS([config.h]) AM_INIT_AUTOMAKE([foreign subdir-objects]) |
|
From: Julian S. <se...@so...> - 2018-10-03 13:32:24
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=3e214c4858a6fdd5697e767543a0c19e30505582 commit 3e214c4858a6fdd5697e767543a0c19e30505582 Author: Julian Seward <js...@ac...> Date: Wed Oct 3 15:29:42 2018 +0200 sigframe construction for x86-linux: ensure that ESP is correctly aligned before entering the handler. n-i-bz. Without this, a signal handler compiled by Clang 6, which uses movdqa to load/store relative to ESP, segfaults because the resulting address isn't 16-aligned. Diff: --- coregrind/m_sigframe/sigframe-x86-linux.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/coregrind/m_sigframe/sigframe-x86-linux.c b/coregrind/m_sigframe/sigframe-x86-linux.c index 27ca4c2..63bcf19 100644 --- a/coregrind/m_sigframe/sigframe-x86-linux.c +++ b/coregrind/m_sigframe/sigframe-x86-linux.c @@ -430,7 +430,7 @@ static Addr build_sigframe(ThreadState *tst, vg_assert((flags & VKI_SA_SIGINFO) == 0); esp -= sizeof(*frame); - esp = VG_ROUNDDN(esp, 16); + esp = VG_ROUNDDN(esp, 16) - 4; frame = (struct sigframe *)esp; if (! ML_(sf_maybe_extend_stack)(tst, esp, sizeof(*frame), flags)) @@ -487,7 +487,7 @@ static Addr build_rt_sigframe(ThreadState *tst, vg_assert((flags & VKI_SA_SIGINFO) != 0); esp -= sizeof(*frame); - esp = VG_ROUNDDN(esp, 16); + esp = VG_ROUNDDN(esp, 16) - 4; frame = (struct rt_sigframe *)esp; if (! ML_(sf_maybe_extend_stack)(tst, esp, sizeof(*frame), flags)) |
|
From: Julian S. <se...@so...> - 2018-10-03 13:29:28
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=617e673e9bd6d4d4d6bc68924e8528a81cca6f7b commit 617e673e9bd6d4d4d6bc68924e8528a81cca6f7b Author: Julian Seward <js...@ac...> Date: Wed Oct 3 15:26:48 2018 +0200 x86 front end: handle UD2 as an officially recognised, unimplemented instruction, like the amd64 front end does. n-i-bz. This doesn't change anything downstream -- a SIGILL is still raised -- but there's a bit less debug printing now. Diff: --- VEX/priv/guest_x86_toIR.c | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/VEX/priv/guest_x86_toIR.c b/VEX/priv/guest_x86_toIR.c index ad1f8d8..2e3b803 100644 --- a/VEX/priv/guest_x86_toIR.c +++ b/VEX/priv/guest_x86_toIR.c @@ -15408,6 +15408,15 @@ DisResult disInstr_X86_WRK ( DIP("syscall\n"); break; + /* =-=-=-=-=-=-=-=-=-=- UD2 =-=-=-=-=-=-=-=-=-=-=-= */ + + case 0x0B: /* UD2 */ + stmt( IRStmt_Put( OFFB_EIP, mkU32(guest_EIP_curr_instr) ) ); + jmp_lit(&dres, Ijk_NoDecode, guest_EIP_curr_instr); + vassert(dres.whatNext == Dis_StopHere); + DIP("ud2\n"); + break; + /* =-=-=-=-=-=-=-=-=- unimp2 =-=-=-=-=-=-=-=-=-=-= */ default: |
|
From: Carl L. <ce...@us...> - 2018-10-01 16:30:26
|
Julian: I was looking to clone the 3.14.0.RC1 tree and test it on PPC64. I did git ls-remote --heads git://sourceware.org/git/valgrind.git but don't see it listed. Just wondering if it in available in a different tree or branch? Carl Love |