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
(9) |
2
(16) |
|
3
(9) |
4
(8) |
5
(9) |
6
(10) |
7
(14) |
8
(10) |
9
(7) |
|
10
(14) |
11
(19) |
12
(22) |
13
(18) |
14
(20) |
15
(10) |
16
(12) |
|
17
(13) |
18
(7) |
19
(12) |
20
(13) |
21
(9) |
22
(12) |
23
(6) |
|
24
(5) |
25
(5) |
26
(6) |
27
(7) |
28
(9) |
29
(13) |
30
(21) |
|
From: Josef W. <Jos...@gm...> - 2006-09-21 19:17:30
|
On Thursday 21 September 2006 18:10, Nicholas Nethercote wrote: > >> Maybe a better solution is to add to the core-tool interface a > >> 'fork-is-happening-now' event which tools can ask to see. Then > >> only the core needs to be able to detect fork-like syscalls. > > > > Yes. I would prefer such a "cleanup_tool_state_after_fork" hook. > > I agree. This is similar to knowing about memory allocated by mmap, etc. > > Here's a possible interface: > > void VG_(track_pre_fork) ( void(*f)(void) ); > void VG_(track_post_fork)( void(*f)(Bool isChild) ); > > So for 'pre_fork' the tool would be told it's about to happen, but no more > information. > > For 'post_fork' the tool would be told it's just happened, and whether it's > the parent or child. Looks good to me. > Is there any other info a tool needs to know when a fork/clone happens? At least, I do not need any more info. I wonder whether it could be useful for the tool in the parent to know about the child PID... Josef |
|
From: Nicholas N. <nj...@cs...> - 2006-09-21 16:26:08
|
On Thu, 21 Sep 2006, Josef Weidendorfer wrote: > > I'm not sure that the scheme of having the tool inspect syscalls > > to detect fork() is going to work cleanly. This is because different > > platforms use different syscalls to do fork, eg Linux does sys_fork > > and sometimes sys_clone, but AIX only does sys_fork, and we don't > > want to force tools to have platform-specific handling like that. > > > > Maybe a better solution is to add to the core-tool interface a > > 'fork-is-happening-now' event which tools can ask to see. Then > > only the core needs to be able to detect fork-like syscalls. > > Yes. I would prefer such a "cleanup_tool_state_after_fork" hook. I agree. This is similar to knowing about memory allocated by mmap/brk/etc. Here's a possible interface for 'pre' and 'post' events: void VG_(track_pre_fork) ( void(*f)(void) ); void VG_(track_post_fork)( void(*f)(Bool isChild) ); So for 'pre_fork' the tool would be told it's about to happen, but no more information. For 'post_fork' the tool would be told it's just happened, and whether it's the parent or child. Is there any other info a tool needs to know when a fork/clone happens? > BTW, cachegrind/massif also should have this kind of "problem", or? I guess so. I'd never thought about it. Nick |
|
From: <sv...@va...> - 2006-09-21 15:59:36
|
Author: njn
Date: 2006-09-21 16:59:30 +0100 (Thu, 21 Sep 2006)
New Revision: 6083
Log:
Add a comment about marking static memory as defined.
Modified:
trunk/memcheck/mc_main.c
Modified: trunk/memcheck/mc_main.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/memcheck/mc_main.c 2006-09-20 21:29:39 UTC (rev 6082)
+++ trunk/memcheck/mc_main.c 2006-09-21 15:59:30 UTC (rev 6083)
@@ -2161,6 +2161,16 @@
void mc_new_mem_startup( Addr a, SizeT len, Bool rr, Bool ww, Bool xx )
{
/* Ignore the permissions, just make it defined. Seems to work... */
+ // Because code is defined, initialised variables get put in the data
+ // segment and are defined, and uninitialised variables get put in th=
e
+ // bss segment and are auto-zeroed (and so defined). =20
+ //
+ // It's possible that there will be padding between global variables.
+ // This will also be auto-zeroed, and marked as defined by Memcheck. =
If
+ // a program uses it, Memcheck will not complain. This is arguably a
+ // false negative, but it's a grey area -- the behaviour is defined (=
the
+ // padding is zeroed) but it's probably not what the user intended. =
And
+ // we can't avoid it.
DEBUG("mc_new_mem_startup(%p, %llu, rr=3D%u, ww=3D%u, xx=3D%u)\n",
a, (ULong)len, rr, ww, xx);
MC_(make_mem_defined)(a, len);
|
|
From: <js...@ac...> - 2006-09-21 12:29:11
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-09-21 09:00:01 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 207 tests, 10 stderr failures, 7 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) none/tests/ppc32/jm-int (stdout) none/tests/ppc32/round (stdout) none/tests/ppc32/round (stderr) none/tests/ppc32/test_fx (stdout) none/tests/ppc32/test_fx (stderr) none/tests/ppc32/test_gx (stdout) |
|
From: Tom H. <to...@co...> - 2006-09-21 02:46:39
|
Nightly build on dunsmere ( athlon, Fedora Core 5 ) started at 2006-09-21 03:30:06 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 240 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2006-09-21 02:26:00
|
Nightly build on dellow ( x86_64, Fedora Core 5 ) started at 2006-09-21 03:10:10 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 268 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2006-09-21 02:24:47
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-09-21 03:15:02 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccpv3Gh8.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccpv3Gh8.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccpv3Gh8.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccpv3Gh8.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccpv3Gh8.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccpv3Gh8.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccpv3Gh8.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccpv3Gh8.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 rm insn_mmx.c insn_sse2.c insn_fpu.c insn_mmxext.c insn_sse.c insn_sse3.c insn_cmov.c insn_basic.c make[5]: Leaving directory `/tmp/valgrind.10464/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.10464/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.10464/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.10464/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.10464/valgrind' make: *** [check] Error 2 ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccu8QfHt.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccu8QfHt.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccu8QfHt.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccu8QfHt.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccu8QfHt.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccu8QfHt.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccu8QfHt.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccu8QfHt.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 rm insn_mmx.c insn_sse2.c insn_fpu.c insn_mmxext.c insn_sse.c insn_sse3.c insn_cmov.c insn_basic.c make[5]: Leaving directory `/tmp/valgrind.10464/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.10464/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.10464/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.10464/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.10464/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Sep 21 03:19:52 2006 --- new.short Thu Sep 21 03:24:42 2006 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccu8QfHt.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccu8QfHt.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccu8QfHt.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccu8QfHt.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccu8QfHt.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccu8QfHt.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccu8QfHt.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccu8QfHt.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 --- 7,16 ---- Last 20 lines of verbose log follow echo ! /tmp/ccpv3Gh8.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccpv3Gh8.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccpv3Gh8.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccpv3Gh8.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccpv3Gh8.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccpv3Gh8.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccpv3Gh8.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccpv3Gh8.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2006-09-21 02:19:32
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2006-09-21 03:05:05 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 268 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leakotron (stdout) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2006-09-21 02:16:44
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-09-21 03:00:03 BST Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 270 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/tls (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 270 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Sep 21 03:08:43 2006 --- new.short Thu Sep 21 03:16:35 2006 *************** *** 8,10 **** ! == 270 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/mempool (stderr) --- 8,10 ---- ! == 270 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) *************** *** 16,17 **** --- 16,18 ---- none/tests/mremap2 (stdout) + none/tests/tls (stdout) |