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...@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 |
|
From: Julian S. <se...@so...> - 2019-04-08 05:20:06
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=b7c807f584733ba98a1a9feec40601ef16389f18 commit b7c807f584733ba98a1a9feec40601ef16389f18 Author: Julian Seward <js...@ac...> Date: Mon Apr 8 07:18:55 2019 +0200 Finalise wording w.r.t. the MPL. Diff: --- dhat/dh_view.js | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/dhat/dh_view.js b/dhat/dh_view.js index d0c56b7..6ccfdf6 100644 --- a/dhat/dh_view.js +++ b/dhat/dh_view.js @@ -29,8 +29,10 @@ /* Parts of this file are derived from Firefox, copyright Mozilla Foundation, - and are subject to the terms of the Mozilla Public License, v. 2.0. A copy - copy of the MPL can be obtained at http://mozilla.org/MPL/2.0/. + and may be redistributed under the terms of the Mozilla Public License + Version 2.0, as well as under the license of this project. A copy of the + Mozilla Public License Version 2.0 is available at at + https://www.mozilla.org/en-US/MPL/2.0/. */ // Test this file by loading dh_view.html?test=1. That runs the tests in |
|
From: Julian S. <js...@ac...> - 2019-04-08 05:17:40
|
Hi, 3.15.0 will be released later this week, all going well. In order to facilitate finalising the release, please don't commit anything without checking first. I hope to make a release-candidate tarball available today/tomorrow. Thanks, J |
|
From: Nicholas N. <nj...@so...> - 2019-04-08 00:21:43
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=b71265fbc9e65936a46158ffb85a5242efbb741e commit b71265fbc9e65936a46158ffb85a5242efbb741e Author: Nicholas Nethercote <nne...@mo...> Date: Mon Apr 8 10:18:38 2019 +1000 Mention --num-callers more in DHAT docs. Diff: --- dhat/docs/dh-manual.xml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index 56f5b6a..da71720 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -67,7 +67,9 @@ Valgrind use, you probably do want to turn optimisation on, since you should profile your program as it will be normally run.</para> <para>Second, you need to run your program under DHAT to gather the profiling -information.</para> +information. You might need to reduce the <option>--num-callers</option> value +to get reasonably-sized output files, especially if you are profiling a large +program; some trial and error might be needed to find a good value.</para> <para>Finally, you need to use DHAT's viewer (in a web browser) to get a detailed presentation of that information.</para> @@ -146,6 +148,10 @@ built with full debugging information.</para> <computeroutput>dh_view.html</computeroutput>. Use the "Load" button to choose a DHAT output file to view.</para> +<para>If loading takes a long time, it might be worth re-running DHAT with a +smaller <option>--num-callers</option> value to reduce the stack depths, +because this can significantly reduce the size of DHAT's output files.</para> + <sect2><title>The Output Header</title> |
|
From: Nicholas N. <nj...@so...> - 2019-04-08 00:21:42
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=19738d1a42ed8fd36b5da0accec29f664437e287 commit 19738d1a42ed8fd36b5da0accec29f664437e287 Author: Nicholas Nethercote <nne...@mo...> Date: Mon Apr 8 10:14:18 2019 +1000 Mention massif-visualizer in the Massif docs. Diff: --- massif/docs/ms-manual.xml | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/massif/docs/ms-manual.xml b/massif/docs/ms-manual.xml index e176dc5..ab377a3 100644 --- a/massif/docs/ms-manual.xml +++ b/massif/docs/ms-manual.xml @@ -647,6 +647,19 @@ in a particular column, which makes following the allocation chains easier. </sect1> +<sect1 id="ms-manual.using" xreflabel="Using massif-visualizer"> +<title>Using massif-visualizer</title> + +<para> +<ulink url="https://github.com/KDE/massif-visualizer">massif-visualizer</ulink> +is a graphical viewer for Massif data that is often easier to use than +ms_print. massif-visualizer is not shipped within Valgrind, but is available in +various places online. +</para> + +</sect1> + + <sect1 id="ms-manual.options" xreflabel="Massif Command-line Options"> <title>Massif Command-line Options</title> |