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
|
3
|
4
|
|
5
(2) |
6
|
7
(1) |
8
(1) |
9
|
10
(1) |
11
|
|
12
(3) |
13
(3) |
14
(3) |
15
(4) |
16
(3) |
17
|
18
(3) |
|
19
(1) |
20
(1) |
21
(3) |
22
|
23
|
24
(1) |
25
(3) |
|
26
|
27
(2) |
28
(10) |
29
|
30
(2) |
31
(2) |
|
|
From: Mark W. <ma...@so...> - 2019-05-15 22:19:27
|
https://sourceware.org/git/gitweb.cgi?p=valgrind.git;h=c212b72a63e43be323a4e028bbdbe8b023c22be8 commit c212b72a63e43be323a4e028bbdbe8b023c22be8 Author: Mark Wielaard <ma...@kl...> Date: Wed May 15 21:30:00 2019 +0200 Explicitly make testcase variable for sys-copy_file_range undefined. On some systems an extra warning could occur when a variable in the memcheck/tests/linux/sys-copy_file_range testcase was undefined, but (accidentially) pointed to known bad memory. Fix by defining the variable as 0, but then marking it explicitly undefined using memcheck VALGRIND_MAKE_MEM_UNDEFINED. Followup for https://bugs.kde.org/show_bug.cgi?id=407218 Diff: --- memcheck/tests/linux/sys-copy_file_range.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/memcheck/tests/linux/sys-copy_file_range.c b/memcheck/tests/linux/sys-copy_file_range.c index 83981c6..589399c 100644 --- a/memcheck/tests/linux/sys-copy_file_range.c +++ b/memcheck/tests/linux/sys-copy_file_range.c @@ -3,8 +3,8 @@ #include <stdio.h> #include <stdlib.h> #include <sys/stat.h> -#include <sys/syscall.h> #include <unistd.h> +#include "../../memcheck.h" int main(int argc, char **argv) { @@ -51,7 +51,7 @@ int main(int argc, char **argv) /* Check valgrind will produce expected warnings for the various wrong arguments. */ do { - void *t; + void *t = 0; VALGRIND_MAKE_MEM_UNDEFINED (&t, sizeof (void *)); void *z = (void *) -1; ret = copy_file_range(fd_in, t, fd_out, NULL, len, 0); |
|
From: Philippe W. <phi...@sk...> - 2019-05-15 22:17:44
|
On Wed, 2019-05-15 at 13:41 +0800, Alex wrote:
> is anyone here?
>
> On Tue, May 14, 2019 at 6:55 PM Alex <zhi...@gm...> wrote:
> > we have have the simple code like this:
> >
> > #include <stdlib.h>
> > int main(int argc, char *argv[])
> > {
> > malloc(10);
> > return 0;
> > }
> >
> > then run `valgrind --leak-check=no --xml=yes --xml-file=x.xml ./main`
> >
> > check the x.xml file, we see:
> >
> > <error>
> > <unique>0x0</unique>
> > <tid>1</tid>
> > <kind>Leak_DefinitelyLost</kind>
> > <xwhat>
> > <text>10 bytes in 1 blocks are definitely lost in loss record 1 of 1</text>
> > <leakedbytes>10</leakedbytes>
> > <leakedblocks>1</leakedblocks>
> > </xwhat>
This is not a bug, it is a feature.
See the below code extracted from mc_main.c:
...
/* If we've been asked to emit XML, mash around various other
options so as to constrain the output somewhat. */
if (VG_(clo_xml)) {
/* Extract as much info as possible from the leak checker. */
MC_(clo_leak_check) = LC_Full;
}
...
The idea is that if you use xml, it means that you have another tool
that extracts/shows/presents/... the information produced by Valgrind,
and so, the filtering of what the 'real end user' wants to see is
to be done by the xml tool, not anymore by Valgrind.
The user manual (e.g. the paragraph that describes --leak-check option
should however describe this behaviour ...
Philippe
|
|
From: John R. <jr...@bi...> - 2019-05-15 14:01:40
|
On Tue, 14 May 2019 18:55:40 +0800, Alex wrote: > we have have the simple code like this: > [[snipped]] On Wed, 15 May 2019 13:41:49 +0800, Alex wrote: > is anyone here? > If it's that urgent (19 hours) then fix it yourself, and include the patch along with the bug report. See the Bug Reports link in the Contact section of http://valgrind.org/ |
|
From: Alex <zhi...@gm...> - 2019-05-15 05:42:22
|
is anyone here?
On Tue, May 14, 2019 at 6:55 PM Alex <zhi...@gm...> wrote:
>
> we have have the simple code like this:
>
> #include <stdlib.h>
> int main(int argc, char *argv[])
> {
> malloc(10);
> return 0;
> }
>
> then run `valgrind --leak-check=no --xml=yes --xml-file=x.xml ./main`
>
> check the x.xml file, we see:
>
> <error>
> <unique>0x0</unique>
> <tid>1</tid>
> <kind>Leak_DefinitelyLost</kind>
> <xwhat>
> <text>10 bytes in 1 blocks are definitely lost in loss record 1 of
> 1</text>
> <leakedbytes>10</leakedbytes>
> <leakedblocks>1</leakedblocks>
> </xwhat>
> <stack>
> <frame>
> <ip>0x4C29E4B</ip>
> <obj>/usr/local/lib/valgrind/vgpreload_memcheck-amd64-linux.so</obj>
> <fn>malloc</fn>
> <dir>/home/yizhi.fzh/valgrind-3.15.0/coregrind/m_replacemalloc</dir>
> <file>vg_replace_malloc.c</file>
> <line>309</line>
> </frame>
> <frame>
> <ip>0x4004FF</ip>
> <obj>/home/yizhi.fzh/github/c-quick-test/main</obj>
> <fn>main</fn>
> <dir>/home/yizhi.fzh/github/c-quick-test</dir>
> <file>main.c</file>
> <line>6</line>
> </frame>
> </stack>
> </error>
>
> $uname -a
> Linux e18c07352.et15sqa 3.10.0-327.ali2008.alios7.x86_64 #1 SMP Tue Nov 29
> 17:56:13 CST 2016 x86_64 x86_64 x86_64 GNU/Linux
>
> $valgrind --version
> valgrind-3.15.0
>
> Thanks
>
|