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
(11) |
2
(8) |
|
3
(8) |
4
(8) |
5
(8) |
6
(19) |
7
(17) |
8
(12) |
9
(10) |
|
10
(15) |
11
(18) |
12
(14) |
13
(16) |
14
(24) |
15
(16) |
16
(12) |
|
17
(25) |
18
(23) |
19
(12) |
20
(10) |
21
(9) |
22
(12) |
23
(13) |
|
24
(19) |
25
(7) |
26
(39) |
27
(22) |
28
(22) |
29
(16) |
30
(13) |
|
31
(23) |
|
|
|
|
|
|
|
From: David G. <gr...@ob...> - 2006-12-22 21:15:23
|
David Greene wrote:
> Is there a version of the watchpoints patch that applies to 3.2.1?
> The version on Robert's page does not.
Urp, I take that back. It does indeed apply. User error.
> I understand the patch is intrusive but it would be really handy
> if a watchpoint capability could be added to the mainline
> distribution. As more and more programs become threaded, gdb
> is going to be less and less useful.
I still stand by this statement. :)
-Dave
|
|
From: David G. <gr...@ob...> - 2006-12-22 21:10:40
|
Is there a version of the watchpoints patch that applies to 3.2.1?
The version on Robert's page does not.
I really need this capability. gdb 6.6 still doesn't understand
how to do watchpoints in the presence of threads so valgrind is
my next best hope.
I understand the patch is intrusive but it would be really handy
if a watchpoint capability could be added to the mainline
distribution. As more and more programs become threaded, gdb
is going to be less and less useful.
-Dave
|
|
From: Josep M. P. C. <jos...@bs...> - 2006-12-22 11:56:59
|
Josef Weidendorfer wrote: > On Thursday 21 December 2006 11:33, Josep M. Perez Cancer wrote: > >> 4. Adding the ability of handling several independent address spaces >> inside valgrind. >> > > VG probably would use one PPU process per PPU/SPU. > No need for supporting independent address spaces. > > It really would be nice to get memcheck working when multiple > processes are communicating via shared memory. Should be possible > when every process runs in VG: They have to share VG's meta > information for the shared address ranges. > > DMA transfers in the case of Cell is probably easy after implementing > the general feature. > > Sharing meta information among different VG processes could even be > a starting point to speed up multithreaded code on multiprocessor > (-core) machines. > I fully agree. That would help and is generic enough to be useful for all platforms. > >> 5. Adding a mechanism to cope with SPU code (and data) that after the >> translation doesn't fit on the SPU memory. >> > > I can not imagine you ever want to run VG itself partly on a SPU. > Why would you? > As you mentioned above, you could think of an SPU thread as an independent process with shared memory and special communication mechanisms. In fact, it is possible to build an SPU binary and run it from the command line. Then it would be nice if we could run memcheck on such a program, specially since the local store does not have memory protection. Furthermore, typically a program that has PPU and SPU parts starts its SPU parts by starting SPU binaries that have been encapsulated into the program itself. In that case, it would help if we could start the main program from memcheck, and then the spawned SPU "threads" could run automatically under memcheck (even if independently). The last step would be to use the shared memory infrastructure that you mentioned to coordinate the PPU and the SPU parts. For example, if the SPU program does a DMA to bring a piece of main memory to its local store, it could also bring in the information regarding that memory. Then the SPU program could run with memory checks. At some point the SPU program may send its output back to main memory. At that point the updated memory information of the output data could also be sent back to the PPU, and the PPU could merge it with its existing information. Josep M. Perez > Josef > |
|
From: Josef W. <Jos...@gm...> - 2006-12-22 11:13:40
|
On Thursday 21 December 2006 11:33, Josep M. Perez Cancer wrote: > 4. Adding the ability of handling several independent address spaces > inside valgrind. VG probably would use one PPU process per PPU/SPU. No need for supporting independent address spaces. It really would be nice to get memcheck working when multiple processes are communicating via shared memory. Should be possible when every process runs in VG: They have to share VG's meta information for the shared address ranges. DMA transfers in the case of Cell is probably easy after implementing the general feature. Sharing meta information among different VG processes could even be a starting point to speed up multithreaded code on multiprocessor (-core) machines. > 5. Adding a mechanism to cope with SPU code (and data) that after the > translation doesn't fit on the SPU memory. I can not imagine you ever want to run VG itself partly on a SPU. Why would you? Josef |
|
From: <js...@ac...> - 2006-12-22 05:26:55
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-12-22 09:00:01 GMT 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 == 215 tests, 10 stderr failures, 6 stdout failures, 0 posttest failures == 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/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) 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: <js...@ac...> - 2006-12-22 05:03:03
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-12-22 04:30:01 GMT Checking out vex source tree ... done Building vex ... done Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 250 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (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. <to...@co...> - 2006-12-22 03:56:20
|
Nightly build on dunsmere ( athlon, Fedora Core 6 ) started at 2006-12-22 03:30:06 GMT 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 == 252 tests, 5 stderr failures, 3 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/pth_detached (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 == 252 tests, 5 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/pth_detached (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri Dec 22 03:43:38 2006 --- new.short Fri Dec 22 03:56:14 2006 *************** *** 8,10 **** ! == 252 tests, 5 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) --- 8,10 ---- ! == 252 tests, 5 stderr failures, 3 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) *************** *** 16,17 **** --- 16,18 ---- none/tests/pth_detached (stdout) + none/tests/tls (stdout) |
|
From: Tom H. <th...@cy...> - 2006-12-22 03:24:03
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-12-22 03:15:03 GMT 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/cc3i6m7J.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc3i6m7J.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc3i6m7J.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc3i6m7J.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc3i6m7J.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc3i6m7J.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc3i6m7J.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc3i6m7J.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.18601/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.18601/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.18601/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.18601/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.18601/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/ccn5xPQ0.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccn5xPQ0.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccn5xPQ0.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccn5xPQ0.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccn5xPQ0.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccn5xPQ0.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccn5xPQ0.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccn5xPQ0.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.18601/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.18601/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.18601/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.18601/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.18601/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri Dec 22 03:19:34 2006 --- new.short Fri Dec 22 03:23:53 2006 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccn5xPQ0.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccn5xPQ0.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccn5xPQ0.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccn5xPQ0.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccn5xPQ0.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccn5xPQ0.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccn5xPQ0.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccn5xPQ0.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/cc3i6m7J.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc3i6m7J.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc3i6m7J.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc3i6m7J.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc3i6m7J.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc3i6m7J.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc3i6m7J.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc3i6m7J.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2006-12-22 03:23:12
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2006-12-22 03:10:05 GMT 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 == 280 tests, 4 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2006-12-22 03:17:50
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2006-12-22 03:05:04 GMT 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 == 280 tests, 5 stderr failures, 1 stdout failure, 0 posttest failures == 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-12-22 03:11:52
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-12-22 03:00:02 GMT 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 == 282 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (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) |
|
From: <js...@ac...> - 2006-12-22 01:29:23
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2006-12-22 02:00:01 CET Results differ from 24 hours ago Checking out valgrind source tree ... failed Last 20 lines of verbose log follow echo Checking out valgrind source tree ... svn co svn://svn.valgrind.org/valgrind/trunk -r {2006-12-22T02:00:01} valgrind svn: Can't connect to host 'svn.valgrind.org': No route to host ================================================= == 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 == 221 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri Dec 22 02:08:11 2006 --- new.short Fri Dec 22 02:08:21 2006 *************** *** 1,18 **** ! Checking out valgrind source tree ... done ! Configuring valgrind ... done ! Building valgrind ... done ! Running regression tests ... failed ! Regression test results follow ! ! == 221 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == ! memcheck/tests/deep_templates (stdout) ! memcheck/tests/leak-cycle (stderr) ! memcheck/tests/leak-tree (stderr) ! memcheck/tests/pointer-trace (stderr) ! none/tests/faultstatus (stderr) ! none/tests/fdleak_cmsg (stderr) ! none/tests/mremap (stderr) ! none/tests/mremap2 (stdout) --- 1,7 ---- ! Checking out valgrind source tree ... failed ! Last 20 lines of verbose log follow echo + Checking out valgrind source tree ... svn co svn://svn.valgrind.org/valgrind/trunk -r {2006-12-22T02:00:01} valgrind + svn: Can't connect to host 'svn.valgrind.org': No route to host |