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
|
2
(1) |
3
(1) |
4
(5) |
5
|
6
(1) |
7
|
|
8
(10) |
9
(7) |
10
(2) |
11
(10) |
12
(1) |
13
|
14
(1) |
|
15
(3) |
16
|
17
|
18
|
19
|
20
|
21
(5) |
|
22
(2) |
23
(2) |
24
(4) |
25
(2) |
26
|
27
(7) |
28
(4) |
|
29
(5) |
30
(5) |
31
(1) |
|
|
|
|
|
From: Paul F. <pa...@so...> - 2023-01-27 19:02:56
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=cbba7f699a830cab23bc0c0a19937ec93994ac39 commit cbba7f699a830cab23bc0c0a19937ec93994ac39 Author: Paul Floyd <pj...@wa...> Date: Fri Jan 27 20:00:26 2023 +0100 Regtest: broaden suppression for helgrind bug 392331 Inlining differences on different Linux platforms. Diff: --- helgrind/tests/bug392331.supp | 23 ++--------------------- 1 file changed, 2 insertions(+), 21 deletions(-) diff --git a/helgrind/tests/bug392331.supp b/helgrind/tests/bug392331.supp index 6b8c5e1174..d19ab70b4a 100644 --- a/helgrind/tests/bug392331.supp +++ b/helgrind/tests/bug392331.supp @@ -1,25 +1,6 @@ { - Check that Dubious suppression works FreeBSD + Check that Dubious suppression works Helgrind:Dubious fun:pthread_cond_signal_WRK - fun:pthread_cond_signal - fun:_ZNSt3__118condition_variable10notify_oneEv -} -{ - Check that Dubious suppression works Linux standalone - Helgrind:Dubious - fun:pthread_cond_signal_WRK - fun:pthread_cond_signal@* - fun:__gthread_cond_signal - fun:UnknownInlinedFun - fun:_ZNSt18condition_variable10notify_oneEv -} -# for some very strange reason the suppression is different -# when running under regtest -{ - Check that Dubious suppression works Linux regtest - Helgrind:Dubious - fun:pthread_cond_signal_WRK - fun:pthread_cond_signal@* - fun:_ZNSt18condition_variable10notify_oneEv + fun:pthread_cond_signal* } |
|
From: Floyd, P. <pj...@wa...> - 2023-01-27 15:08:42
|
Hi On 27/01/2023 08:19, Julian Seward wrote: > On 25/01/2023 21:16, Paul Floyd wrote: >> I'd like some feedback on >> >> https://bugs.kde.org/show_bug.cgi?id=464103 >> >> This allows the user to specify that a block of memory should be >> histogrammed. [..] > > I can see that the request tells dhat to start tracking the area. How > does it > know when to stop tracking? And what happens if the area happens to > overlap > an existing area? I didn't have any plans for stopping - just leave that to DHAT to stop when the memory is feeed/reallocd. > > Rather than specify exactly the bounds of the area in the macro (that > is, both > address and length), would it be preferable to just specify the base > address > of the block, in the expectation that the block is one that the > program has > previously obtained from malloc, and hence one that dhat already knows > about? > Good idea. I was just copying the code that creates the blocks and propagating the arguments back out to the client requests. > In this case, the macro is merely a request to say "please histogram > this block even though it's above the 1024 limit". That seems to me > at least to > be a simple mental model for end users. For the [start, +len) > formulation in > the existing patch, I'm unclear how that interacts with the "normal" > machinery > of tracking only blocks that come from malloc. My intention is this this to be an override for the 1024 limit. I'll remove the size argument. A+ Paul |
|
From: Paul F. <pa...@so...> - 2023-01-27 07:42:40
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=f7e4bb4af294575432b629de4869812fdfee6feb commit f7e4bb4af294575432b629de4869812fdfee6feb Author: Paul Floyd <pj...@wa...> Date: Fri Jan 27 08:42:06 2023 +0100 Bug 382034 - Testcases build fixes for musl Diff: --- NEWS | 1 + memcheck/tests/arm64-linux/scalar.h | 4 ++++ memcheck/tests/x86-linux/scalar.h | 4 ++++ none/tests/x86-linux/seg_override.c | 11 +++++++++-- 4 files changed, 18 insertions(+), 2 deletions(-) diff --git a/NEWS b/NEWS index 9c2410d89a..7990a8a56f 100644 --- a/NEWS +++ b/NEWS @@ -78,6 +78,7 @@ are not entered into bugzilla tend to get forgotten about or ignored. 170510 Don't warn about ioctl of size 0 without direction hint 241072 List tools in --help output 327548 false positive while destroying mutex +382034 Testcases build fixes for musl 351857 confusing error message about valid command line option 392331 Spurious lock not held error from inside pthread_cond_timedwait 400793 pthread_rwlock_timedwrlock false positive diff --git a/memcheck/tests/arm64-linux/scalar.h b/memcheck/tests/arm64-linux/scalar.h index 9008816d6e..8ef050f4b0 100644 --- a/memcheck/tests/arm64-linux/scalar.h +++ b/memcheck/tests/arm64-linux/scalar.h @@ -12,6 +12,10 @@ #include <sys/types.h> #include <sys/mman.h> +#ifndef __THROW +#define __THROW +#endif + // Since we use vki_unistd.h, we can't include <unistd.h>. So we have to // declare this ourselves. extern long int syscall (long int __sysno, ...) __THROW; diff --git a/memcheck/tests/x86-linux/scalar.h b/memcheck/tests/x86-linux/scalar.h index ef28b03550..52f742e4ac 100644 --- a/memcheck/tests/x86-linux/scalar.h +++ b/memcheck/tests/x86-linux/scalar.h @@ -11,6 +11,10 @@ #include <sys/types.h> #include <sys/mman.h> +#ifndef __THROW +#define __THROW +#endif + // Since we use vki_unistd.h, we can't include <unistd.h>. So we have to // declare this ourselves. extern long int syscall (long int __sysno, ...) __THROW; diff --git a/none/tests/x86-linux/seg_override.c b/none/tests/x86-linux/seg_override.c index b7619c9a80..ca8fbfe2b2 100644 --- a/none/tests/x86-linux/seg_override.c +++ b/none/tests/x86-linux/seg_override.c @@ -2,6 +2,8 @@ #include <stdio.h> #include <errno.h> #include <string.h> +#include "../../../config.h" + /* Stuff from Wine. */ @@ -52,14 +54,19 @@ inline static unsigned int wine_ldt_get_limit( const LDT_ENTRY *ent ) /* our copy of the ldt */ LDT_ENTRY ldt_copy[8192]; +#if defined(MUSL_LIBC) +#define MODIFY_LDT(func, ptr, bytecount) syscall(SYS_modify_ldt, (func), (ptr), (bytecount) ); +#else +#define MODIFY_LDT(func, ptr, bytecount) __modify_ldt((func), (ptr), (bytecount) ); /* System call to set LDT entry. */ //extern int __modify_ldt (int, struct modify_ldt_ldt_s *, size_t); extern int __modify_ldt (int, void *, size_t); +#endif void print_ldt ( void ) { int res; - res = __modify_ldt( 0, ldt_copy, 8192*sizeof(LDT_ENTRY) ); + res = MODIFY_LDT( 0, ldt_copy, 8192*sizeof(LDT_ENTRY) ); printf("got %d bytes\n", res ); perror("error is"); } @@ -102,7 +109,7 @@ void set_ldt1 ( void* base ) ldt_entry.read_exec_only = 0; ldt_entry.limit_in_pages = 0; ldt_entry.seg_not_present = 0; - stat = __modify_ldt (1, &ldt_entry, sizeof (ldt_entry)); + stat = MODIFY_LDT (1, &ldt_entry, sizeof (ldt_entry)); printf("stat = %d\n", stat); } |
|
From: Paul F. <pa...@so...> - 2023-01-27 07:32:04
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=dee222c6e818ca43ac45952fc8a020f445d98781 commit dee222c6e818ca43ac45952fc8a020f445d98781 Author: Paul Floyd <pj...@wa...> Date: Fri Jan 27 08:30:41 2023 +0100 Bug 464859 - Build failures with GCC-13 (drd tsan_unittest) Patch submitted by Khem Raj <raj...@gm...> Diff: --- NEWS | 1 + drd/tests/tsan_thread_wrappers_pthread.h | 1 + 2 files changed, 2 insertions(+) diff --git a/NEWS b/NEWS index 02296575c4..9c2410d89a 100644 --- a/NEWS +++ b/NEWS @@ -91,6 +91,7 @@ are not entered into bugzilla tend to get forgotten about or ignored. 462830 WARNING: unhandled amd64-freebsd syscall: 474 463027 broken check for MPX instruction support in assembler 464476 Firefox fails to start under Valgrind +464859 Build failures with GCC-13 (drd tsan_unittest) To see details of a given bug, visit https://bugs.kde.org/show_bug.cgi?id=XXXXXX diff --git a/drd/tests/tsan_thread_wrappers_pthread.h b/drd/tests/tsan_thread_wrappers_pthread.h index f15e6ad631..4cc8062069 100644 --- a/drd/tests/tsan_thread_wrappers_pthread.h +++ b/drd/tests/tsan_thread_wrappers_pthread.h @@ -55,6 +55,7 @@ #define NO_TLS #endif +#include <cstdint> #include <string> using namespace std; |
|
From: Paul F. <pa...@so...> - 2023-01-27 07:24:28
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=57c1641d042e7554143c11af3b52f2efc924ace4 commit 57c1641d042e7554143c11af3b52f2efc924ace4 Author: Paul Floyd <pj...@wa...> Date: Fri Jan 27 08:22:19 2023 +0100 Linux regtest: some extra filtering for helgrind bug392331 Was failing on rhel 7.6 Diff: --- helgrind/tests/Makefile.am | 4 +++- helgrind/tests/bug392331.stderr.exp | 6 ------ helgrind/tests/bug392331.vgtest | 1 + helgrind/tests/filter_bug392331 | 12 ++++++++++++ 4 files changed, 16 insertions(+), 7 deletions(-) diff --git a/helgrind/tests/Makefile.am b/helgrind/tests/Makefile.am index 0a8bd5744b..65f18f1435 100755 --- a/helgrind/tests/Makefile.am +++ b/helgrind/tests/Makefile.am @@ -6,7 +6,9 @@ dist_noinst_SCRIPTS = filter_stderr \ filter_helgrind \ filter_xml \ filter_freebsd.awk \ - filter_stderr_freebsd + filter_stderr_freebsd \ + filter_bug392331 + EXTRA_DIST = \ annotate_hbefore.vgtest annotate_hbefore.stdout.exp \ diff --git a/helgrind/tests/bug392331.stderr.exp b/helgrind/tests/bug392331.stderr.exp index f278e3b089..b61e64f40d 100644 --- a/helgrind/tests/bug392331.stderr.exp +++ b/helgrind/tests/bug392331.stderr.exp @@ -7,15 +7,12 @@ Thread #x is the program's root thread Thread #x: pthread_cond_{signal,broadcast}: dubious: associated lock is not held by any thread at 0x........: pthread_cond_signal_WRK (hg_intercepts.c:...) by 0x........: pthread_cond_signal (hg_intercepts.c:...) - ... by 0x........: main (bug392331.cpp:47) ---Thread-Announcement------------------------------------------ Thread #x was created - ... by 0x........: pthread_create@* (hg_intercepts.c:...) - ... by 0x........: main (bug392331.cpp:38) ---------------------------------------------------------------- @@ -23,9 +20,6 @@ Thread #x was created Thread #x: pthread_cond_{signal,broadcast}: dubious: associated lock is not held by any thread at 0x........: pthread_cond_signal_WRK (hg_intercepts.c:...) by 0x........: pthread_cond_signal (hg_intercepts.c:...) - ... by 0x........: worker_thread() (bug392331.cpp:33) - ... by 0x........: mythread_wrapper (hg_intercepts.c:...) - ... diff --git a/helgrind/tests/bug392331.vgtest b/helgrind/tests/bug392331.vgtest index c160dcd40e..3889b15f77 100644 --- a/helgrind/tests/bug392331.vgtest +++ b/helgrind/tests/bug392331.vgtest @@ -1,3 +1,4 @@ prereq: test -e bug392331 vgopts: -q prog: bug392331 +stderr_filter: filter_bug392331 diff --git a/helgrind/tests/filter_bug392331 b/helgrind/tests/filter_bug392331 new file mode 100755 index 0000000000..9cbd5d04e2 --- /dev/null +++ b/helgrind/tests/filter_bug392331 @@ -0,0 +1,12 @@ +#! /bin/sh + +# at least on fedora 3{6|7} the first stanza contains +# by 0x........: pthread_cond_signal (hg_intercepts.c:...) +# ... +# but on rhel 7.6 at least there is no ellipsis +# To make life easier, filter all of them not just the first + +./filter_stderr "$@" | + +sed '/^ \.\.\./d' + |
|
From: Julian S. <jse...@gm...> - 2023-01-27 07:19:17
|
On 25/01/2023 21:16, Paul Floyd wrote: > I'd like some feedback on > > https://bugs.kde.org/show_bug.cgi?id=464103 > > This allows the user to specify that a block of memory should be histogrammed. [..] I can see that the request tells dhat to start tracking the area. How does it know when to stop tracking? And what happens if the area happens to overlap an existing area? Rather than specify exactly the bounds of the area in the macro (that is, both address and length), would it be preferable to just specify the base address of the block, in the expectation that the block is one that the program has previously obtained from malloc, and hence one that dhat already knows about? In this case, the macro is merely a request to say "please histogram this block even though it's above the 1024 limit". That seems to me at least to be a simple mental model for end users. For the [start, +len) formulation in the existing patch, I'm unclear how that interacts with the "normal" machinery of tracking only blocks that come from malloc. J |
|
From: Paul F. <pa...@so...> - 2023-01-27 06:41:37
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=0df691f9d9a8538ea34a4c535f45d30e0f77d60f commit 0df691f9d9a8538ea34a4c535f45d30e0f77d60f Author: Paul Floyd <pj...@wa...> Date: Fri Jan 27 07:40:31 2023 +0100 Linux regtest: forgot prereq test for scalar_openat2 Diff: --- memcheck/tests/x86-linux/scalar_openat2.vgtest | 1 + 1 file changed, 1 insertion(+) diff --git a/memcheck/tests/x86-linux/scalar_openat2.vgtest b/memcheck/tests/x86-linux/scalar_openat2.vgtest index 517c797e61..8f27ad11d0 100644 --- a/memcheck/tests/x86-linux/scalar_openat2.vgtest +++ b/memcheck/tests/x86-linux/scalar_openat2.vgtest @@ -1,2 +1,3 @@ +prereq: test -e ./scalar_openat2 prog: scalar_openat2 vgopts: -q |