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
(1) |
3
(1) |
4
(2) |
5
(2) |
6
|
|
7
(3) |
8
(14) |
9
(3) |
10
(7) |
11
(7) |
12
(1) |
13
(3) |
|
14
|
15
|
16
(6) |
17
(2) |
18
(6) |
19
(3) |
20
|
|
21
|
22
(1) |
23
|
24
|
25
|
26
|
27
(1) |
|
28
|
29
|
30
|
|
|
|
|
|
From: Mark W. <ma...@so...> - 2019-04-11 16:08:32
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=535d2ff4f2f755faa8b1a9e467833eca455bd2d7 commit 535d2ff4f2f755faa8b1a9e467833eca455bd2d7 Author: Mark Wielaard <ma...@kl...> Date: Thu Apr 11 18:06:34 2019 +0200 none/tests/amd64-linux/map_32bits.vgtest fails too easily On various systems none/tests/amd64-linux/map_32bits.vgtest fails with: first mmap: Cannot allocate memory. The problem is that the --aspace-minaddr is too tight. Newer glibc seem to mmap some memory and so even our first mmap with MMAP_32BIT will fail. The solution is to make a bit more memory < 2GB available. If there is 16MB available the test always seems to succeed without needing too many tries. The original 256K is too low. https://bugs.kde.org/show_bug.cgi?id=406422 Diff: --- NEWS | 1 + none/tests/amd64-linux/map_32bits.vgtest | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 7faba7e..bf7b3dd 100644 --- a/NEWS +++ b/NEWS @@ -152,6 +152,7 @@ where XXXXXX is the bug number as listed below. 406355 mcsignopass, mcsigpass, mcbreak fail due to difference in gdb output 406357 gdbserver_tests fails because of gdb output change 406360 memcheck/tests/libstdc++.supp needs more supression variants +406422 none/tests/amd64-linux/map_32bits.vgtest fails too easily n-i-bz add syswrap for PTRACE_GET|SET_THREAD_AREA on amd64. n-i-bz Fix callgrind_annotate non deterministic order for equal total n-i-bz callgrind_annotate --threshold=100 does not print all functions. diff --git a/none/tests/amd64-linux/map_32bits.vgtest b/none/tests/amd64-linux/map_32bits.vgtest index 2b7f3a0..43011e3 100644 --- a/none/tests/amd64-linux/map_32bits.vgtest +++ b/none/tests/amd64-linux/map_32bits.vgtest @@ -1,5 +1,5 @@ prog: map_32bits # take a big aspacemgr minaddr, to quickly reach the 2GB limit -vgopts: -q --aspace-minaddr=0x7ff60000 +vgopts: -q --aspace-minaddr=0x7f000000 stderr_filter: filter_stderr |
|
From: Mark W. <ma...@so...> - 2019-04-11 16:05:29
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=eacf885df231037fd6a02ada7a7cafb44ce6b89c commit eacf885df231037fd6a02ada7a7cafb44ce6b89c Author: Mark Wielaard <ma...@kl...> Date: Thu Apr 11 18:01:24 2019 +0200 filter_libc: remove the line holding the futex syscall error entirely The current filter might leave empty lines behind. This is caused by the fact that glibc used to not include a newline in the message. But since glibc 2.29 it does. https://bugs.kde.org/show_bug.cgi?id=405205 Reported-by: Stefan Maksimovic <ste...@rt...> Diff: --- NEWS | 1 + tests/filter_libc | 2 ++ 2 files changed, 3 insertions(+) diff --git a/NEWS b/NEWS index a4a459d..7faba7e 100644 --- a/NEWS +++ b/NEWS @@ -129,6 +129,7 @@ where XXXXXX is the bug number as listed below. 404888 autotools cleanup series 405079 unhandled ppc64le-linux syscall: 131 (quotactl) 405182 Valgrind fails to build with Clang +405205 filter_libc: remove the line holding the futex syscall error entirely 405356 PPC64, xvcvsxdsp, xvcvuxdsp are supposed to write the 32-bit result to the upper and lower 32-bits of the 64-bit result 405362 PPC64, vmsummbm instruction doesn't handle overflow case correctly diff --git a/tests/filter_libc b/tests/filter_libc index 9607db5..8eb9911 100755 --- a/tests/filter_libc +++ b/tests/filter_libc @@ -37,6 +37,8 @@ while (<>) s/(at.*)operator delete\[\]\(void\*\)/$1...operator delete[].../; # Some glibc versions complain about unexpected futex syscall errors. + # With or without newline (see sourceware PR20271). + next if /^The futex facility returned an unexpected error code.$/; s/The futex facility returned an unexpected error code.//; print; |
|
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: 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: Julian S. <se...@so...> - 2019-04-11 07:17:57
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=45d3fef65e20aaf9bf845314e474097dc643c8ba commit 45d3fef65e20aaf9bf845314e474097dc643c8ba Author: Julian Seward <js...@ac...> Date: Thu Apr 11 09:16:40 2019 +0200 -> 3.15.0.RC2 Diff: --- NEWS | 4 ++-- configure.ac | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index 34228b4..a4a459d 100644 --- a/NEWS +++ b/NEWS @@ -151,14 +151,14 @@ where XXXXXX is the bug number as listed below. 406355 mcsignopass, mcsigpass, mcbreak fail due to difference in gdb output 406357 gdbserver_tests fails because of gdb output change 406360 memcheck/tests/libstdc++.supp needs more supression variants - n-i-bz add syswrap for PTRACE_GET|SET_THREAD_AREA on amd64. n-i-bz Fix callgrind_annotate non deterministic order for equal total n-i-bz callgrind_annotate --threshold=100 does not print all functions. n-i-bz callgrind_annotate Use of uninitialized value in numeric gt (>) n-i-bz amd64 (x86_64): RDRAND and F16C insn set extensions are supported -(3.15.0.RC1: 8 April 2019, git ce94d674de5b99df173aad4c3ee48fc2a92e5d9c) +(3.15.0.RC1: 8 April 2019, git ce94d674de5b99df173aad4c3ee48fc2a92e5d9c) +(3.15.0.RC2: 11 April 2019, git 0c8be9bbede189ec580ec270521811766429595f) diff --git a/configure.ac b/configure.ac index 8eea766..3d85010 100755 --- a/configure.ac +++ b/configure.ac @@ -8,7 +8,7 @@ ##------------------------------------------------------------## # Process this file with autoconf to produce a configure script. -AC_INIT([Valgrind],[3.15.0.RC1],[val...@li...]) +AC_INIT([Valgrind],[3.15.0.RC2],[val...@li...]) AC_CONFIG_SRCDIR(coregrind/m_main.c) AC_CONFIG_HEADERS([config.h]) AM_INIT_AUTOMAKE([foreign dist-bzip2 subdir-objects]) |
|
From: Mark W. <ma...@so...> - 2019-04-10 17:34:54
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=0c8be9bbede189ec580ec270521811766429595f commit 0c8be9bbede189ec580ec270521811766429595f Author: Mark Wielaard <ma...@kl...> Date: Wed Apr 10 01:28:24 2019 +0200 gdbserver_tests fails because of gdb output change. The 'done.' in "Reading symbols from <exe>...done." is optional. https://bugs.kde.org/show_bug.cgi?id=406357 Reported-by: Roger Light <ro...@at...> Diff: --- NEWS | 1 + gdbserver_tests/filter_gdb | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 795a19b..34228b4 100644 --- a/NEWS +++ b/NEWS @@ -149,6 +149,7 @@ where XXXXXX is the bug number as listed below. 406352 cachegrind/callgrind fails ann tests because of missing a.c 406354 dhat is broken on x86 (32bit) 406355 mcsignopass, mcsigpass, mcbreak fail due to difference in gdb output +406357 gdbserver_tests fails because of gdb output change 406360 memcheck/tests/libstdc++.supp needs more supression variants n-i-bz add syswrap for PTRACE_GET|SET_THREAD_AREA on amd64. diff --git a/gdbserver_tests/filter_gdb b/gdbserver_tests/filter_gdb index 947e7bc..6eff229 100755 --- a/gdbserver_tests/filter_gdb +++ b/gdbserver_tests/filter_gdb @@ -92,7 +92,7 @@ sed -e '/Remote debugging using/,/vgdb launched process attached/d' -e 's/^Thread .... received /Program received /' \ -e 's/#[0-9]\( 0x........ in sleeper_or_burner\)/#.\1/' \ -e 's/\(#0 0x........ in do_burn ()\) at sleepers.c:41/\1/' \ - -e '/^Reading symbols from .*\.\.\.done\./d' \ + -e '/^Reading symbols from .*\.\.\.\(done\.\)\?/d' \ -e '/^Loaded symbols for .*$/d' \ -e '/^Current language.*/d' \ -e '/^The current source language is.*/d' \ |
|
From: Mark W. <ma...@so...> - 2019-04-10 17:01:23
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=12addd06445a1685e91ff091867ae27d6eac733f commit 12addd06445a1685e91ff091867ae27d6eac733f Author: Alexandra Hájková <aha...@re...> Date: Tue Apr 9 11:09:56 2019 +0200 gdbserver_tests: adjust filtering for the new gdb output mcsigpass and mcsignopass tests fails due to the slightly different gdb output. Filter the tests output to make it the same for different gdb version. Change mcsigpass and mcsignopass .exp to fit filtered .out. More generic regexp by Stefan Maksimovic <ste...@rt...>. https://bugs.kde.org/show_bug.cgi?id=406355 Diff: --- NEWS | 1 + gdbserver_tests/filter_gdb | 1 + gdbserver_tests/mcbreak.stdoutB.exp | 4 ++-- gdbserver_tests/mcinfcallWSRU.stderrB.exp | 2 +- gdbserver_tests/mcsignopass.stdoutB.exp | 24 ++++++++++++------------ gdbserver_tests/mcsigpass.stdoutB.exp | 6 +++--- gdbserver_tests/nlcontrolc.stdoutB.exp | 2 +- 7 files changed, 21 insertions(+), 19 deletions(-) diff --git a/NEWS b/NEWS index 6f420ca..795a19b 100644 --- a/NEWS +++ b/NEWS @@ -148,6 +148,7 @@ where XXXXXX is the bug number as listed below. bit in output. 406352 cachegrind/callgrind fails ann tests because of missing a.c 406354 dhat is broken on x86 (32bit) +406355 mcsignopass, mcsigpass, mcbreak fail due to difference in gdb output 406360 memcheck/tests/libstdc++.supp needs more supression variants n-i-bz add syswrap for PTRACE_GET|SET_THREAD_AREA on amd64. diff --git a/gdbserver_tests/filter_gdb b/gdbserver_tests/filter_gdb index 05bbe4c..947e7bc 100755 --- a/gdbserver_tests/filter_gdb +++ b/gdbserver_tests/filter_gdb @@ -139,6 +139,7 @@ sed -e '/Remote debugging using/,/vgdb launched process attached/d' -e 's/VgTs_WaitSys) 0x/VgTs_WaitSys) 0x/' \ -e '/Cannot access memory at address 0x......../d' \ -e '/\[New Thread/d' \ + -e 's/^0x........ in \(\w\+ (\)/\1/' \ -e '/^$/d' | # remove all the lines telling where the SIGFPE was trapped. diff --git a/gdbserver_tests/mcbreak.stdoutB.exp b/gdbserver_tests/mcbreak.stdoutB.exp index ba526da..7559037 100644 --- a/gdbserver_tests/mcbreak.stdoutB.exp +++ b/gdbserver_tests/mcbreak.stdoutB.exp @@ -43,11 +43,11 @@ Breakpoint 3, main (argc=1, argv=0x........) at t.c:120 Delete all breakpoints? (y or n) [answered Y; input not from terminal] Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in make_error (s=0x........ "called from level") at t.c:41 +make_error (s=0x........ "called from level") at t.c:41 41 if (int_und == 0) 44 printf ("%s int_und is not zero\n", s); old_pc has changed after step Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in make_error (s=0x........ "called from main") at t.c:41 +make_error (s=0x........ "called from main") at t.c:41 41 if (int_und == 0) diff --git a/gdbserver_tests/mcinfcallWSRU.stderrB.exp b/gdbserver_tests/mcinfcallWSRU.stderrB.exp index a2f2b87..06dc433 100644 --- a/gdbserver_tests/mcinfcallWSRU.stderrB.exp +++ b/gdbserver_tests/mcinfcallWSRU.stderrB.exp @@ -14,7 +14,7 @@ Breakpoint 1, sleeper_or_burner (v=0x........) at sleepers.c:74 74 int i = 0; Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in do_burn () at sleepers.c:41 +do_burn () at sleepers.c:41 41 for (i = 0; i < burn; i++) loopnr++; [Switching to thread 1 (Thread ....)] #0 0x........ in do_burn () diff --git a/gdbserver_tests/mcsignopass.stdoutB.exp b/gdbserver_tests/mcsignopass.stdoutB.exp index d77f983..18c830b 100644 --- a/gdbserver_tests/mcsignopass.stdoutB.exp +++ b/gdbserver_tests/mcsignopass.stdoutB.exp @@ -6,54 +6,54 @@ Signal Stop Print Pass to program Description SIGFPE Yes Yes Yes Arithmetic exception Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Signal Stop Print Pass to program Description SIGSEGV No Yes Yes Segmentation fault Continuing. Program received signal SIGSEGV, Segmentation fault. Program received signal SIGBUS, Bus error. -0x........ in test3 () at faultstatus.c:126 +test3 () at faultstatus.c:126 126 mapping[FILESIZE+10]; Continuing. Program received signal SIGFPE, Arithmetic exception. diff --git a/gdbserver_tests/mcsigpass.stdoutB.exp b/gdbserver_tests/mcsigpass.stdoutB.exp index de6c263..6800358 100644 --- a/gdbserver_tests/mcsigpass.stdoutB.exp +++ b/gdbserver_tests/mcsigpass.stdoutB.exp @@ -1,14 +1,14 @@ Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test1 () at faultstatus.c:116 +test1 () at faultstatus.c:116 116 *BADADDR = 'x'; Continuing. Program received signal SIGSEGV, Segmentation fault. -0x........ in test2 () at faultstatus.c:121 +test2 () at faultstatus.c:121 121 mapping[0] = 'x'; Continuing. Program received signal SIGBUS, Bus error. -0x........ in test3 () at faultstatus.c:126 +test3 () at faultstatus.c:126 126 mapping[FILESIZE+10]; Continuing. Program received signal SIGFPE, Arithmetic exception. diff --git a/gdbserver_tests/nlcontrolc.stdoutB.exp b/gdbserver_tests/nlcontrolc.stdoutB.exp index e334fd0..e8a5ff8 100644 --- a/gdbserver_tests/nlcontrolc.stdoutB.exp +++ b/gdbserver_tests/nlcontrolc.stdoutB.exp @@ -9,7 +9,7 @@ $4 = 0 changed burning parameters Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. -0x........ in do_burn () at sleepers.c:41 +do_burn () at sleepers.c:41 41 for (i = 0; i < burn; i++) loopnr++; $5 = 0 $6 = 0 |
|
From: Mark W. <ma...@so...> - 2019-04-10 15:08:52
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=4960f47c7dc39032a216c41b991dd138b91e5e5d commit 4960f47c7dc39032a216c41b991dd138b91e5e5d Author: Mark Wielaard <ma...@kl...> Date: Wed Apr 10 01:22:37 2019 +0200 dhat is broken on x86 (32bit) dhat will crash on x86 (32bit) because it doesn't handle Vg_CoreClientReq in its track_post_mem_write. dh_handle_noninsn_write will be called with Vg_CoreClientReq during shutdown when trying to setup an argument for the freeres_wrapper(). On other architectures this will be done through a register, but on x86 we setup the argument on the stack. See final_tidyup () in coregrind/m_main.c. Just handle it like a syscall memory argument write. https://bugs.kde.org/show_bug.cgi?id=406354 Diff: --- NEWS | 1 + dhat/dh_main.c | 1 + 2 files changed, 2 insertions(+) diff --git a/NEWS b/NEWS index 2cc8d20..6f420ca 100644 --- a/NEWS +++ b/NEWS @@ -147,6 +147,7 @@ where XXXXXX is the bug number as listed below. 406198 none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output. 406352 cachegrind/callgrind fails ann tests because of missing a.c +406354 dhat is broken on x86 (32bit) 406360 memcheck/tests/libstdc++.supp needs more supression variants n-i-bz add syswrap for PTRACE_GET|SET_THREAD_AREA on amd64. diff --git a/dhat/dh_main.c b/dhat/dh_main.c index 47a9327..a933328 100644 --- a/dhat/dh_main.c +++ b/dhat/dh_main.c @@ -794,6 +794,7 @@ void dh_handle_noninsn_write ( CorePart part, ThreadId tid, { switch (part) { case Vg_CoreSysCall: + case Vg_CoreClientReq: dh_handle_write(base, size); break; case Vg_CoreSignal: |
|
From: Mark W. <ma...@so...> - 2019-04-10 15:08:46
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=69cbd01e748d161daf5416e1bb969d3530f96335 commit 69cbd01e748d161daf5416e1bb969d3530f96335 Author: Mark Wielaard <ma...@kl...> Date: Tue Apr 9 16:09:50 2019 +0200 More memcheck/tests/libstdc++.supp suppressions memcheck/tests/leak_cpp_interior might fail because depending on compiler and arch used the suppression file used doesn't catch some allocations through the DT_INIT_ARRAY functions. That memory doesn't actually leak, it gets freed by the __gnu_cxx::__freeres hook. But since this testcase shows leaks while running, not after the program ends, it needs to suppress these allocations. https://bugs.kde.org/show_bug.cgi?id=406360 Diff: --- NEWS | 1 + memcheck/tests/libstdc++.supp | 23 +++++++++++++++++++++++ 2 files changed, 24 insertions(+) diff --git a/NEWS b/NEWS index 6f99183..2cc8d20 100644 --- a/NEWS +++ b/NEWS @@ -147,6 +147,7 @@ where XXXXXX is the bug number as listed below. 406198 none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output. 406352 cachegrind/callgrind fails ann tests because of missing a.c +406360 memcheck/tests/libstdc++.supp needs more supression variants n-i-bz add syswrap for PTRACE_GET|SET_THREAD_AREA on amd64. n-i-bz Fix callgrind_annotate non deterministic order for equal total diff --git a/memcheck/tests/libstdc++.supp b/memcheck/tests/libstdc++.supp index fad537f..28ab182 100644 --- a/memcheck/tests/libstdc++.supp +++ b/memcheck/tests/libstdc++.supp @@ -49,6 +49,9 @@ # still reachable: 72,704 bytes in 1 blocks # suppressed: 0 bytes in 0 blocks +# All the following suppressions are variants of +# _dl_init -> call_init which calls the DT_INIT_ARRAY functions + { malloc-leaks-cxx-stl-string-classes Memcheck:Leak @@ -61,6 +64,16 @@ obj:*lib*/ld-2.*.so } { + malloc-leaks-cxx-stl-string-classes-2 + Memcheck:Leak + match-leak-kinds: reachable + fun:malloc + obj:*lib*/libstdc++.so* + fun:call_init.part.0 + fun:_dl_init + obj:*lib*/ld-2.*.so +} +{ malloc-leaks-cxx-stl-string-classes-debug Memcheck:Leak match-leak-kinds: reachable @@ -73,3 +86,13 @@ fun:_dl_init obj:*lib*/ld-2.*.so } +{ + malloc-leaks-cxx-stl-string-classes-debug2 + Memcheck:Leak + match-leak-kinds: reachable + fun:malloc + obj:* + fun:call_init + fun:_dl_init + fun:_dl_start_user +} |
|
From: Mark W. <ma...@so...> - 2019-04-10 15:01:47
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=08f20ed4afadf6134ca7e164416e98a1a60e0baa commit 08f20ed4afadf6134ca7e164416e98a1a60e0baa Author: Mark Wielaard <ma...@kl...> Date: Tue Apr 9 14:47:05 2019 +0200 Add missing cachegrind/tests/a.c to EXTRA_DIST. cachegrind/callgrind fails ann[12] tests because of missing a.c These testcases fail because the dist tar is missing the a.c (auto-annotated) source file. Fix by adding it to EXTRA_DIST. https://bugs.kde.org/show_bug.cgi?id=406352 Diff: --- NEWS | 1 + cachegrind/tests/Makefile.am | 6 +++--- 2 files changed, 4 insertions(+), 3 deletions(-) diff --git a/NEWS b/NEWS index 535b86e..6f99183 100644 --- a/NEWS +++ b/NEWS @@ -146,6 +146,7 @@ where XXXXXX is the bug number as listed below. 405782 "VEX temporary storage exhausted" when attempting to debug slic3r-pe 406198 none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output. +406352 cachegrind/callgrind fails ann tests because of missing a.c n-i-bz add syswrap for PTRACE_GET|SET_THREAD_AREA on amd64. n-i-bz Fix callgrind_annotate non deterministic order for equal total diff --git a/cachegrind/tests/Makefile.am b/cachegrind/tests/Makefile.am index f2f8902..571ae22 100644 --- a/cachegrind/tests/Makefile.am +++ b/cachegrind/tests/Makefile.am @@ -10,8 +10,8 @@ DIST_SUBDIRS = x86 . dist_noinst_SCRIPTS = filter_stderr filter_cachesim_discards -# Note that test.c is not compiled. It just serves as input for cg_annotate in -# ann1 and ann2. +# Note that test.c and a.c are not compiled. +# They just serve as input for cg_annotate in ann1 and ann2. EXTRA_DIST = \ cgout-test \ ann1.post.exp ann1.stderr.exp ann1.vgtest \ @@ -20,7 +20,7 @@ EXTRA_DIST = \ clreq.vgtest clreq.stderr.exp \ dlclose.vgtest dlclose.stderr.exp dlclose.stdout.exp \ notpower2.vgtest notpower2.stderr.exp \ - test.c \ + test.c a.c \ wrap5.vgtest wrap5.stderr.exp wrap5.stdout.exp check_PROGRAMS = \ |
|
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: 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: 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-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-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: 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. |
|
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: Julian S. <se...@so...> - 2019-04-08 12:32:26
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=b2d2da64b0de1c4d657b63187967b68606e84711 commit b2d2da64b0de1c4d657b63187967b68606e84711 Author: Julian Seward <js...@ac...> Date: Mon Apr 8 14:16:48 2019 +0200 GET_STARTREGS for s390: fix register constraint (per comments from Andreas Arnez). Diff: --- coregrind/m_libcassert.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/coregrind/m_libcassert.c b/coregrind/m_libcassert.c index 6d1cd4c..bb9b92b 100644 --- a/coregrind/m_libcassert.c +++ b/coregrind/m_libcassert.c @@ -180,7 +180,7 @@ "std %%f6, 72(%1);" \ "std %%f7, 80(%1);" \ : /* out */ "=r" (ia) \ - : /* in */ "r" (&block[0]) \ + : /* in */ "a" (&block[0]) \ : /* trash */ "memory" \ ); \ (srP)->r_pc = ia; \ |
|
From: Andreas A. <ar...@li...> - 2019-04-08 11:08:53
|
On Fri, Apr 05 2019, Julian Seward wrote: > https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=d36ea889d8d8a1646be… > > commit d36ea889d8d8a1646be85c30ab5771af6912b7a1 > Author: Julian Seward <jse...@pu...> > Date: Fri Apr 5 20:10:46 2019 +0200 > > Bug 404843 - s390x: backtrace sometimes ends prematurely. Thanks again for taking care of this. > [...] > --- a/coregrind/m_libcassert.c > +++ b/coregrind/m_libcassert.c > @@ -163,19 +163,38 @@ > [...] > + "std %%f5, 64(%1);" \ > + "std %%f6, 72(%1);" \ > + "std %%f7, 80(%1);" \ > + : /* out */ "=r" (ia) \ > + : /* in */ "r" (&block[0]) \ This "r" should be an "a" instead. For "r" the compiler could theoretically choose %r0, which wouldn't do what we want. The "=r" above is OK, because "brasl" works with %r0 as well. > + : /* trash */ "memory" \ Fine by me. Normally I prefer to be more precise (as shown in my proposal), but I guess it doesn't matter here. -- Andreas |
|
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: Julian S. <se...@so...> - 2019-04-08 08:18:41
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=d847ab5f5bd53c9cd78e5531ebfac8648fdf0b5e commit d847ab5f5bd53c9cd78e5531ebfac8648fdf0b5e Author: Julian Seward <js...@ac...> Date: Mon Apr 8 10:16:18 2019 +0200 -> 3.15.0.RC1 Diff: --- NEWS | 2 +- configure.ac | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 0a0e410..535b86e 100644 --- a/NEWS +++ b/NEWS @@ -153,7 +153,7 @@ n-i-bz callgrind_annotate --threshold=100 does not print all functions. n-i-bz callgrind_annotate Use of uninitialized value in numeric gt (>) n-i-bz amd64 (x86_64): RDRAND and F16C insn set extensions are supported -(3.15.0.RC1: XX April 2019, git xx) +(3.15.0.RC1: 8 April 2019, git ce94d674de5b99df173aad4c3ee48fc2a92e5d9c) diff --git a/configure.ac b/configure.ac index e26b503..8eea766 100755 --- a/configure.ac +++ b/configure.ac @@ -8,7 +8,7 @@ ##------------------------------------------------------------## # Process this file with autoconf to produce a configure script. -AC_INIT([Valgrind],[3.15.0.GIT],[val...@li...]) +AC_INIT([Valgrind],[3.15.0.RC1],[val...@li...]) AC_CONFIG_SRCDIR(coregrind/m_main.c) AC_CONFIG_HEADERS([config.h]) AM_INIT_AUTOMAKE([foreign dist-bzip2 subdir-objects]) |
|
From: Julian S. <se...@so...> - 2019-04-08 07:29:35
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=ce94d674de5b99df173aad4c3ee48fc2a92e5d9c commit ce94d674de5b99df173aad4c3ee48fc2a92e5d9c Author: Julian Seward <js...@ac...> Date: Mon Apr 8 09:29:03 2019 +0200 Fix broken links in the Massif manual. Diff: --- docs/xml/manual-core.xml | 4 ++-- massif/docs/ms-manual.xml | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml index cb21089..141a13c 100644 --- a/docs/xml/manual-core.xml +++ b/docs/xml/manual-core.xml @@ -3033,8 +3033,8 @@ the "Massif Format".</para> <para>Different Massif Format file visualisers are available. Valgrind distribution includes the <option>ms_print</option> command line utility that produces an easy to read reprentation of - a massif output file. See <xref linkend="ms-manual.running-massif"/> and - <xref linkend="ms-manual.using"/> for more details + a massif output file. See <xref linkend="ms-manual.using-print"/> and + <xref linkend="ms-manual.using-visualizer"/> for more details about visualising Massif Format output files.</para> <para>Note that xtree Massif Format makes use of the inline information when specifying <option>--read-inline-info=yes</option>. diff --git a/massif/docs/ms-manual.xml b/massif/docs/ms-manual.xml index ab377a3..cc99025 100644 --- a/massif/docs/ms-manual.xml +++ b/massif/docs/ms-manual.xml @@ -54,7 +54,7 @@ which parts of your program are responsible for allocating the heap memory. </sect1> -<sect1 id="ms-manual.using" xreflabel="Using Massif and ms_print"> +<sect1 id="ms-manual.using-print" xreflabel="Using Massif and ms_print"> <title>Using Massif and ms_print</title> <para>First off, as for the other Valgrind tools, you should compile with @@ -647,7 +647,7 @@ in a particular column, which makes following the allocation chains easier. </sect1> -<sect1 id="ms-manual.using" xreflabel="Using massif-visualizer"> +<sect1 id="ms-manual.using-visualizer" xreflabel="Using massif-visualizer"> <title>Using massif-visualizer</title> <para> |
|
From: Julian S. <se...@so...> - 2019-04-08 06:11:24
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=832ff31c815e2c9372a2a87a94cbf4064fd24aa9 commit 832ff31c815e2c9372a2a87a94cbf4064fd24aa9 Author: Julian Seward <js...@ac...> Date: Mon Apr 8 08:08:19 2019 +0200 Misc doc updates for upcoming 3.15.0 release. Diff: --- NEWS | 48 +++++++++++++++++++++++----------------- README | 7 ++++-- docs/internals/release-HOWTO.txt | 2 +- docs/xml/vg-entities.xml | 6 ++--- 4 files changed, 37 insertions(+), 26 deletions(-) diff --git a/NEWS b/NEWS index 0e95407..0a0e410 100644 --- a/NEWS +++ b/NEWS @@ -1,5 +1,6 @@ -Release 3.15.0 (?? ??????? 2019) -~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + +Release 3.15.0 (12 April 2019) +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 3.15.0 is a feature release with many improvements and the usual collection of bug fixes. @@ -8,29 +9,29 @@ This release supports X86/Linux, AMD64/Linux, ARM32/Linux, ARM64/Linux, PPC32/Linux, PPC64BE/Linux, PPC64LE/Linux, S390X/Linux, MIPS32/Linux, MIPS64/Linux, ARM/Android, ARM64/Android, MIPS32/Android, X86/Android, X86/Solaris, AMD64/Solaris and AMD64/MacOSX 10.12. There is also preliminary -support for X86/macOS 10.13, AMD64/macOS 10.13. +support for X86/macOS 10.13 and AMD64/macOS 10.13. * ==================== CORE CHANGES =================== * The XTree Massif output format now makes use of the information obtained when specifying --read-inline-info=yes. -* ================== PLATFORM CHANGES ================= - +* amd64 (x86_64): the RDRAND and F16C insn set extensions are now supported. * ==================== TOOL CHANGES ==================== * DHAT: - - DHAT been thoroughly overhauled and improved. As a result, it has been - promoted from an experimental tool to a regular tool. Run it with - --tool=dhat instead of --tool=exp-dhat. + - DHAT been thoroughly overhauled, improved, and given a GUI. As a result, + it has been promoted from an experimental tool to a regular tool. Run it + with --tool=dhat instead of --tool=exp-dhat. - DHAT now prints only minimal data when the program ends, instead writing - the bulk of the profiling data to a file. As a result, the --show-top-n and - --sort-by options have been removed. + the bulk of the profiling data to a file. As a result, the --show-top-n + and --sort-by options have been removed. - - Data files can be viewed with the new viewer, dh_view.html. + - Profile results can be viewed with the new viewer, dh_view.html. When + a run ends, a short message is printed, explaining how to view the result. - See the documentation for more details. @@ -48,23 +49,28 @@ support for X86/macOS 10.13, AMD64/macOS 10.13. sort the caller/callee lists in the call tree. * Massif: + - The default value for --read-inline-info is now "yes" on Linux/Android/Solaris. It is still "no" on other OS. * Memcheck: + - The option --xtree-leak=yes (to output leak result in xtree format) - automatically activates the option --show-leak-kinds=all, - as xtree visualisation tools such as kcachegrind can in any case - select what kind of leak to visualise. + automatically activates the option --show-leak-kinds=all, as xtree + visualisation tools such as kcachegrind can in any case select what kind + of leak to visualise. + + - There has been further work to avoid false positives. In particular, + integer equality on partially defined inputs (C == and !=) is now handled + better. * ==================== OTHER CHANGES ==================== -* The new option --show-error-list=no|yes - allows to show at exit the list of detected errors and the used - suppressions. In the previous valgrind version, showing this - information could only be done using a verbosity >= 2, which is - producing a lot of other non necessarily useful messages. - The option -s is equivalent to --show-error-list=yes. +* The new option --show-error-list=no|yes displays, at the end of the run, the + list of detected errors and the used suppressions. Prior to this change, + showing this information could only be done by specifying "-v -v", which is + also produced a lot of other possibly-non-useful messages. The option -s is + equivalent to --show-error-list=yes. * ==================== FIXED BUGS ==================== @@ -147,6 +153,8 @@ n-i-bz callgrind_annotate --threshold=100 does not print all functions. n-i-bz callgrind_annotate Use of uninitialized value in numeric gt (>) n-i-bz amd64 (x86_64): RDRAND and F16C insn set extensions are supported +(3.15.0.RC1: XX April 2019, git xx) + Release 3.14.0 (9 October 2018) diff --git a/README b/README index 6f333d3..0d3ac1d 100644 --- a/README +++ b/README @@ -37,6 +37,7 @@ platforms: - PPC32/Linux - PPC64/Linux - ARM/Linux +- ARM64/Linux - x86/macOS - AMD64/macOS - S390X/Linux @@ -67,7 +68,9 @@ Building and installing it ~~~~~~~~~~~~~~~~~~~~~~~~~~ To install from the GIT repository: - 0. Clone the code from GIT, following the instructions at + 0. Clone the code from GIT: + git clone git://sourceware.org/git/valgrind.git + There are further instructions at http://www.valgrind.org/downloads/repository.html. 1. cd into the source directory. @@ -89,7 +92,7 @@ To install from a tar.bz2 distribution: 7. See if it works. Try "valgrind ls -l". Either this works, or it bombs out with some complaint. In that case, please let us know - (see www.valgrind.org). + (see http://valgrind.org/support/bug_reports.html). Important! Do not move the valgrind installation into a place different from that specified by --prefix at build time. This will diff --git a/docs/internals/release-HOWTO.txt b/docs/internals/release-HOWTO.txt index 3516013..45cc41a 100644 --- a/docs/internals/release-HOWTO.txt +++ b/docs/internals/release-HOWTO.txt @@ -105,7 +105,7 @@ releases, bug-fix-only releases might not need one): * s390x: Ensure README.s390 is up-to-date and URLs therein are not stale. -- Change release number in AC_INIT() in configure.in to "X.Y.Z-rcN", where +- Change release number in AC_INIT() in configure.ac to "X.Y.Z-rcN", where 'N' is the release candidate number. - Make the tarball ("make dist") and put it on the web somewhere (it doesn't diff --git a/docs/xml/vg-entities.xml b/docs/xml/vg-entities.xml index 1bae979..fc5629d 100644 --- a/docs/xml/vg-entities.xml +++ b/docs/xml/vg-entities.xml @@ -2,12 +2,12 @@ <!ENTITY vg-jemail "ju...@va..."> <!ENTITY vg-vemail "val...@va..."> <!ENTITY cl-email "Jos...@gm..."> -<!ENTITY vg-lifespan "2000-2018"> +<!ENTITY vg-lifespan "2000-2019"> <!-- valgrind release + version stuff --> <!ENTITY rel-type "Release"> -<!ENTITY rel-version "3.15.0.GIT"> -<!ENTITY rel-date "?? ???? 2019"> +<!ENTITY rel-version "3.15.0"> +<!ENTITY rel-date "12 April 2019"> <!-- where the docs are installed --> <!ENTITY vg-docs-path "$INSTALL/share/doc/valgrind/html/index.html"> |
|
From: Julian S. <se...@so...> - 2019-04-08 06:08:04
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=9a8e749a7d3851aae0f35e1f0927ecb3238b6b27 commit 9a8e749a7d3851aae0f35e1f0927ecb3238b6b27 Author: Julian Seward <js...@ac...> Date: Mon Apr 8 08:07:39 2019 +0200 Update __VALGRIND_MINOR__ for the upcoming 3.15 release. Diff: --- include/valgrind.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/valgrind.h b/include/valgrind.h index 577c8f0..cc8c2b8 100644 --- a/include/valgrind.h +++ b/include/valgrind.h @@ -89,7 +89,7 @@ || (__VALGRIND_MAJOR__ == 3 && __VALGRIND_MINOR__ >= 6)) */ #define __VALGRIND_MAJOR__ 3 -#define __VALGRIND_MINOR__ 14 +#define __VALGRIND_MINOR__ 15 #include <stdarg.h> |
|
From: Julian S. <se...@so...> - 2019-04-08 05:22:56
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=40f8eb8d4c0f2f738dafddc3ccbac70b0232e912 commit 40f8eb8d4c0f2f738dafddc3ccbac70b0232e912 Author: Julian Seward <js...@ac...> Date: Mon Apr 8 07:22:28 2019 +0200 Finalise bug-fix status notes. Diff: --- NEWS | 3 ++- docs/internals/3_14_BUGSTATUS.txt | 17 +++-------------- 2 files changed, 5 insertions(+), 15 deletions(-) diff --git a/NEWS b/NEWS index 9a1e9dd..0e95407 100644 --- a/NEWS +++ b/NEWS @@ -119,6 +119,7 @@ where XXXXXX is the bug number as listed below. 403552 s390x: wrong facility bit checked for vector facility 404054 memcheck powerpc subfe x, x, x initializes x to 0 or -1 based on CA 404638 Add VG_(replaceIndexXA) +404843 s390x: backtrace sometimes ends prematurely 404888 autotools cleanup series 405079 unhandled ppc64le-linux syscall: 131 (quotactl) 405182 Valgrind fails to build with Clang @@ -132,11 +133,11 @@ where XXXXXX is the bug number as listed below. 405430 Use gcc -Wimplicit-fallthrough=2 by default if available 405458 MIPS mkFormVEC arguments swapped? 405716 drd: Fix an integer overflow in the stack margin calculation +405722 Support arm64 core dump 405733 PPC64, xvcvdpsp should write 32-bit result to upper and lower 32-bits of the 64-bit destination field. 405734 PPC64, vrlwnm, vrlwmi, vrldrm, vrldmi do not work properly when me < mb 405782 "VEX temporary storage exhausted" when attempting to debug slic3r-pe -405722 Support arm64 core dump 406198 none/tests/ppc64/test_isa_3_0_other test sporadically including CA bit in output. diff --git a/docs/internals/3_14_BUGSTATUS.txt b/docs/internals/3_14_BUGSTATUS.txt index c909de6..a934f18 100644 --- a/docs/internals/3_14_BUGSTATUS.txt +++ b/docs/internals/3_14_BUGSTATUS.txt @@ -16,9 +16,6 @@ doesn't carry over bugs from earlier versions. === Debuginfo reader =================================================== -404843*8 s390x: backtrace sometimes ends prematurely - Should try to fix for 3.15.0 - 405295 valgrind 3.14.0 dies due to mysterious DWARF information? (output from rust used by Mozilla TB.) But possibly only when --read-var-info=yes @@ -105,8 +102,6 @@ doesn't carry over bugs from earlier versions. == 381819 398545 Support for SHA instruction on Ryzen -398870* Please add support for instruction vcvtps2ph - 400538* vex amd64->IR: 0x48 0xCF 0xF 0x1F 0x0 0xFF 0xD2 0xCC 0x90 0x55 Should fix (Wine/Windows) This is IRETQ. Are we expecting that to work at all in user space? @@ -124,13 +119,6 @@ doesn't carry over bugs from earlier versions. === VEX/mips =========================================================== === VEX/other ========================================================== === VEX/ppc ============================================================ - -401827 none/tests/ppc64/test_isa_2_06_part3 failure on ppc64le (xvrsqrtesp) - Possible testcase bug -401828 none/tests/ppc64/test_isa_2_06_part1 failure on ppc64le (fcfids and - fcfidus) - Possible testcase bug - === VEX/s390x ========================================================== 404076 s390x: z14 vector instructions not implemented @@ -171,7 +159,7 @@ doesn't carry over bugs from earlier versions. === zz_other/Win32 ===================================================== === zz_other/x86 ======================================================= -400099** Memcheck produces truncated backtrace when len(argv + env) = 4096 +400099* Memcheck produces truncated backtrace when len(argv + env) = 4096 Possible stack overrun problem; should investigate ======================================================================== @@ -183,7 +171,8 @@ Mon 3 Sep 12:01:52 CEST 2018 Support RDPMC* ? Improve PDB* reading ? I thought I saw some patches for this .. is it 253657 ? -Remove FSGSBASE from CPUID +apply included fixes for Xen 4.6/4.7/4.8/4.9/4.10/4.11/4.12 390553 ? + Sat 9 Mar 18:48:58 CET 2019 |