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: Josef W. <Jos...@gm...> - 2006-12-19 10:25:06
|
On Tuesday 19 December 2006 03:39, Julian Seward wrote: > > I wonder if I can use a constant factor to keep my polling for a command > > file happening at regular intervals, yet not producing too much overhead. > > I suppose I misused this VG_TRACK(thread_run) event ... > > One simple solution is for VG_TRACK(thread_run) to take a second argument, > which is a 64-bit number, the total number of blocks executed by V so far. > By comparing this number against the number in the previous call you can > find out how much progress the system made in between. Then you could > base your polling decisions on that. How does that sound? Oh, that sounds very good. But do we need to change the signature of VG_TRACK(thread_run) for this? I still think that I am only misusing this event for my polling. Especially, the event does not trigger when the valgrind process sleeps. So a solution which waits for commands e.g. on a socket would be far better. It would be nice to have a function VG_(blocks_done)() or similar to get the total number of blocks executed so far. I have something like this in callgrind myself; but of course it is not incremented when callgrind is in "no instrumentation" mode; still, the command polling has to work to allow to switch on instrumentation. Josef > > J > |
|
From: <js...@ac...> - 2006-12-19 05:14:37
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-12-19 09: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 == 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-19 04:54:58
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-12-19 04:30:02 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) ================================================= == Results from 24 hours ago == ================================================= 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 Last 20 lines of verbose log follow echo pth_detached.c:12: error: syntax error before 's_spinlock' pth_detached.c:12: warning: type defaults to 'int' in declaration of 's_spinlock' pth_detached.c:12: warning: data definition has no type or storage class pth_detached.c: In function 'increment_finished_count': pth_detached.c:16: warning: implicit declaration of function 'pthread_spin_lock' pth_detached.c:18: warning: implicit declaration of function 'pthread_spin_unlock' pth_detached.c: In function 'main': pth_detached.c:53: warning: implicit declaration of function 'pthread_spin_init' pth_detached.c:87: warning: implicit declaration of function 'pthread_spin_destroy' make[5]: *** [pth_detached.o] Error 1 make[5]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/home/sewardj/Nightly/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/sewardj/Nightly/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Dec 19 04:39:08 2006 --- new.short Tue Dec 19 04:55:07 2006 *************** *** 8,29 **** ! Last 20 lines of verbose log follow echo ! pth_detached.c:12: error: syntax error before 's_spinlock' ! pth_detached.c:12: warning: type defaults to 'int' in declaration of 's_spinlock' ! pth_detached.c:12: warning: data definition has no type or storage class ! pth_detached.c: In function 'increment_finished_count': ! pth_detached.c:16: warning: implicit declaration of function 'pthread_spin_lock' ! pth_detached.c:18: warning: implicit declaration of function 'pthread_spin_unlock' ! pth_detached.c: In function 'main': ! pth_detached.c:53: warning: implicit declaration of function 'pthread_spin_init' ! pth_detached.c:87: warning: implicit declaration of function 'pthread_spin_destroy' ! make[5]: *** [pth_detached.o] Error 1 ! make[5]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests' ! make[4]: *** [check-am] Error 2 ! make[4]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests' ! make[3]: *** [check-recursive] Error 1 ! make[3]: Leaving directory `/home/sewardj/Nightly/valgrind/none/tests' ! make[2]: *** [check-recursive] Error 1 ! make[2]: Leaving directory `/home/sewardj/Nightly/valgrind/none' ! make[1]: *** [check-recursive] Error 1 ! make[1]: Leaving directory `/home/sewardj/Nightly/valgrind' ! make: *** [check] Error 2 --- 8,19 ---- ! 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-19 03:55:30
|
Nightly build on dunsmere ( athlon, Fedora Core 6 ) started at 2006-12-19 03:30: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 == 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) |
|
From: Tom H. <th...@cy...> - 2006-12-19 03:24:12
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-12-19 03:15:05 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/ccgRYXMB.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccgRYXMB.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccgRYXMB.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccgRYXMB.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccgRYXMB.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccgRYXMB.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccgRYXMB.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccgRYXMB.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.31066/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.31066/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.31066/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.31066/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.31066/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 pth_detached.c:12: parse error before "s_spinlock" pth_detached.c:12: warning: type defaults to `int' in declaration of `s_spinlock' pth_detached.c:12: warning: data definition has no type or storage class pth_detached.c: In function `increment_finished_count': pth_detached.c:16: warning: implicit declaration of function `pthread_spin_lock' pth_detached.c:18: warning: implicit declaration of function `pthread_spin_unlock' pth_detached.c: In function `main': pth_detached.c:53: warning: implicit declaration of function `pthread_spin_init' pth_detached.c:87: warning: implicit declaration of function `pthread_spin_destroy' make[5]: *** [pth_detached.o] Error 1 make[5]: Leaving directory `/tmp/valgrind.31066/valgrind/none/tests' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.31066/valgrind/none/tests' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.31066/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.31066/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.31066/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Dec 19 03:19:40 2006 --- new.short Tue Dec 19 03:24:00 2006 *************** *** 7,21 **** Last 20 lines of verbose log follow echo ! pth_detached.c:12: parse error before "s_spinlock" ! pth_detached.c:12: warning: type defaults to `int' in declaration of `s_spinlock' ! pth_detached.c:12: warning: data definition has no type or storage class ! pth_detached.c: In function `increment_finished_count': ! pth_detached.c:16: warning: implicit declaration of function `pthread_spin_lock' ! pth_detached.c:18: warning: implicit declaration of function `pthread_spin_unlock' ! pth_detached.c: In function `main': ! pth_detached.c:53: warning: implicit declaration of function `pthread_spin_init' ! pth_detached.c:87: warning: implicit declaration of function `pthread_spin_destroy' ! make[5]: *** [pth_detached.o] Error 1 ! make[5]: Leaving directory `/tmp/valgrind.31066/valgrind/none/tests' make[4]: *** [check-am] Error 2 ! make[4]: Leaving directory `/tmp/valgrind.31066/valgrind/none/tests' make[3]: *** [check-recursive] Error 1 --- 7,21 ---- Last 20 lines of verbose log follow echo ! /tmp/ccgRYXMB.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccgRYXMB.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccgRYXMB.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccgRYXMB.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccgRYXMB.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccgRYXMB.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccgRYXMB.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccgRYXMB.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.31066/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 ! make[4]: Leaving directory `/tmp/valgrind.31066/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 |
|
From: Tom H. <th...@cy...> - 2006-12-19 03:23:27
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2006-12-19 03:10:03 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-19 03:13:39
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2006-12-19 03:05:05 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 == 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) ================================================= == 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 pth_detached.c:12: error: syntax error before "s_spinlock" pth_detached.c:12: warning: type defaults to `int' in declaration of `s_spinlock' pth_detached.c:12: warning: data definition has no type or storage class pth_detached.c: In function `increment_finished_count': pth_detached.c:16: warning: implicit declaration of function `pthread_spin_lock' pth_detached.c:18: warning: implicit declaration of function `pthread_spin_unlock' pth_detached.c: In function `main': pth_detached.c:53: warning: implicit declaration of function `pthread_spin_init' pth_detached.c:87: warning: implicit declaration of function `pthread_spin_destroy' make[5]: *** [pth_detached.o] Error 1 make[5]: Leaving directory `/tmp/valgrind.15963/valgrind/none/tests' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.15963/valgrind/none/tests' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.15963/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.15963/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.15963/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Dec 19 03:07:46 2006 --- new.short Tue Dec 19 03:13:27 2006 *************** *** 6,27 **** ! Last 20 lines of verbose log follow echo ! pth_detached.c:12: error: syntax error before "s_spinlock" ! pth_detached.c:12: warning: type defaults to `int' in declaration of `s_spinlock' ! pth_detached.c:12: warning: data definition has no type or storage class ! pth_detached.c: In function `increment_finished_count': ! pth_detached.c:16: warning: implicit declaration of function `pthread_spin_lock' ! pth_detached.c:18: warning: implicit declaration of function `pthread_spin_unlock' ! pth_detached.c: In function `main': ! pth_detached.c:53: warning: implicit declaration of function `pthread_spin_init' ! pth_detached.c:87: warning: implicit declaration of function `pthread_spin_destroy' ! make[5]: *** [pth_detached.o] Error 1 ! make[5]: Leaving directory `/tmp/valgrind.15963/valgrind/none/tests' ! make[4]: *** [check-am] Error 2 ! make[4]: Leaving directory `/tmp/valgrind.15963/valgrind/none/tests' ! make[3]: *** [check-recursive] Error 1 ! make[3]: Leaving directory `/tmp/valgrind.15963/valgrind/none/tests' ! make[2]: *** [check-recursive] Error 1 ! make[2]: Leaving directory `/tmp/valgrind.15963/valgrind/none' ! make[1]: *** [check-recursive] Error 1 ! make[1]: Leaving directory `/tmp/valgrind.15963/valgrind' ! make: *** [check] Error 2 --- 6,16 ---- ! 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-19 03:09:00
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-12-19 03:00:02 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 == 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) ================================================= == 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 pth_detached.c:12: error: syntax error before "s_spinlock" pth_detached.c:12: warning: type defaults to `int' in declaration of `s_spinlock' pth_detached.c:12: warning: data definition has no type or storage class pth_detached.c: In function `increment_finished_count': pth_detached.c:16: warning: implicit declaration of function `pthread_spin_lock' pth_detached.c:18: warning: implicit declaration of function `pthread_spin_unlock' pth_detached.c: In function `main': pth_detached.c:53: warning: implicit declaration of function `pthread_spin_init' pth_detached.c:87: warning: implicit declaration of function `pthread_spin_destroy' make[5]: *** [pth_detached.o] Error 1 make[5]: Leaving directory `/tmp/valgrind.20889/valgrind/none/tests' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.20889/valgrind/none/tests' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.20889/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.20889/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.20889/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Dec 19 03:02:50 2006 --- new.short Tue Dec 19 03:08:43 2006 *************** *** 6,27 **** ! Last 20 lines of verbose log follow echo ! pth_detached.c:12: error: syntax error before "s_spinlock" ! pth_detached.c:12: warning: type defaults to `int' in declaration of `s_spinlock' ! pth_detached.c:12: warning: data definition has no type or storage class ! pth_detached.c: In function `increment_finished_count': ! pth_detached.c:16: warning: implicit declaration of function `pthread_spin_lock' ! pth_detached.c:18: warning: implicit declaration of function `pthread_spin_unlock' ! pth_detached.c: In function `main': ! pth_detached.c:53: warning: implicit declaration of function `pthread_spin_init' ! pth_detached.c:87: warning: implicit declaration of function `pthread_spin_destroy' ! make[5]: *** [pth_detached.o] Error 1 ! make[5]: Leaving directory `/tmp/valgrind.20889/valgrind/none/tests' ! make[4]: *** [check-am] Error 2 ! make[4]: Leaving directory `/tmp/valgrind.20889/valgrind/none/tests' ! make[3]: *** [check-recursive] Error 1 ! make[3]: Leaving directory `/tmp/valgrind.20889/valgrind/none/tests' ! make[2]: *** [check-recursive] Error 1 ! make[2]: Leaving directory `/tmp/valgrind.20889/valgrind/none' ! make[1]: *** [check-recursive] Error 1 ! make[1]: Leaving directory `/tmp/valgrind.20889/valgrind' ! make: *** [check] Error 2 --- 6,17 ---- ! 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: Julian S. <js...@ac...> - 2006-12-19 02:29:50
|
> I understand that in the beginning with lots of translations, > VG_TRACK(thread_run) will be called _very_ often now. Yes. > But it looks that > later, in the steady case, the frequency will go down. Yes. > Is it right that at the moment, VG_TRACK(thread_run) will simply be > called after a fixed number of translated blocks are executed? Well, mostly, but you can't rely on it. At the moment, VG_TRACK(thread_run) is called when a thread gets the CPU lock. Ownership of the lock can change not only because of exceeding the 100k-block quota, but also if a thread does syscalls or takes a signal. > I wonder if I can use a constant factor to keep my polling for a command > file happening at regular intervals, yet not producing too much overhead. > I suppose I misused this VG_TRACK(thread_run) event ... One simple solution is for VG_TRACK(thread_run) to take a second argument, which is a 64-bit number, the total number of blocks executed by V so far. By comparing this number against the number in the previous call you can find out how much progress the system made in between. Then you could base your polling decisions on that. How does that sound? J |
|
From: Josef W. <Jos...@gm...> - 2006-12-19 01:19:04
|
On Tuesday 19 December 2006 01:18, Julian Seward wrote: > > > VG_TRACK(thread_run)(tid) means "thread tid has the CPU lock and is > > > about to start running client code". > > > > > > VG_TRACK(thread_stopped)(tid) means "thread tid, which previously had the > > > CPU lock and was running client code, is no longer running client code." > > > > So the difference is that now if translation is happening, I get a > > VG_TRACK(thread_stopped) before, and after the translation has finished, > > I get a VG_TRACK(thread_run), even when not switching client threads? > > That is correct (at least, that is what I am proposing based on what > Bart needs.) Ok. > Is that ok for you or do you need some different behaviour? I understand that in the beginning with lots of translations, VG_TRACK(thread_run) will be called _very_ often now. But it looks that later, in the steady case, the frequency will go down. Is it right that at the moment, VG_TRACK(thread_run) will simply be called after a fixed number of translated blocks are executed? I wonder if I can use a constant factor to keep my polling for a command file happening at regular intervals, yet not producing too much overhead. I suppose I misused this VG_TRACK(thread_run) event ... Josef |
|
From: <js...@ac...> - 2006-12-19 01:16:35
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2006-12-19 02:00:01 CET 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 == 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) |
|
From: Julian S. <js...@ac...> - 2006-12-19 00:08:51
|
Hi Josef. Thanks for the analysis. > Ok, I tried to reconstruct it. > It was at VG 2.x times. There actually were 2 problems: > (1) SK_(post_signal) was not being called exhaustively for the > case that a signal handler was left via longjmp. And callgrind > needs a signal handler exit event. > I can not see how (also 3.x) VG ever could catch this event, as > the signal frame is discarded by the longjmp. I agree. > However, this > has nothing to do with > (2) There was a problem in older VG 2.x releases about not > notifying the tool about current thread after running a > signal handler in another thread. I think this was fixed, > and probably is not a problem at all in VG 3.x. Good. I agree, this is probably fixed. > > VG_TRACK(thread_run)(tid) means "thread tid has the CPU lock and is > > about to start running client code". > > > > VG_TRACK(thread_stopped)(tid) means "thread tid, which previously had the > > CPU lock and was running client code, is no longer running client code." > > So the difference is that now if translation is happening, I get a > VG_TRACK(thread_stopped) before, and after the translation has finished, > I get a VG_TRACK(thread_run), even when not switching client threads? That is correct (at least, that is what I am proposing based on what Bart needs.) Is that ok for you or do you need some different behaviour? Obviously this change will go only in the trunk and not on the 3.2 branch. J |