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: Nicholas N. <nj...@cs...> - 2006-12-07 21:41:19
|
On Thu, 7 Dec 2006, Josef Weidendorfer wrote: > However, I thought it should be possible to optionally provide wrappers > in coregrind, and the tool can specify if it want it enabled or not. > Or is this not possible? That's basically what Julian's suggestion achieves. The tool-writer has to write the wrappers separately for each tool, so it's not as convenient as ticking a box, but it's not that much code and we so far only have one tool that needs pthread_* wrapprs. Nick |
|
From: Josef W. <Jos...@gm...> - 2006-12-07 17:24:45
|
On Thursday 07 December 2006 14:05, Bart Van Assche wrote: > > On a quick look at that, I notice(d before now) your pthread_* function > > wrappers are in coregrind/vg_preloaded.c. I would prefer that those > > wrappers be placed in a drd-specific its own preload .so, in the same > > way that memcheck has its malloc wrappers placed in its own .so, > > vgpreload_memcheck-<platform>.so. > > This has two advantages: (1) it avoids forcing all tools to use the pthread > > wrappers when they don't need to, which avoids a potentially large performance > > loss I think the one reason for not making wrappers tool-global is, that e.g. for cachegrind or callgrind, these wrappers actually can appear quite high on the cost list of functions, depending on application behavior. Especially for the malloc wrappers and for malloc-intensive C++ applications, you originally saw valgrinds own malloc replacements on top of your profile. And that can not be correct: you want to see the behavior of the malloc versions in your C runtime library. However, I thought it should be possible to optionally provide wrappers in coregrind, and the tool can specify if it want it enabled or not. Or is this not possible? Josef |
|
From: <sv...@va...> - 2006-12-07 15:34:15
|
Author: dirk Date: 2006-12-07 15:34:04 +0000 (Thu, 07 Dec 2006) New Revision: 6385 Log: backport build fix from trunk Modified: branches/VALGRIND_3_2_BRANCH/Makefile.am Modified: branches/VALGRIND_3_2_BRANCH/Makefile.am =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 --- branches/VALGRIND_3_2_BRANCH/Makefile.am 2006-12-07 15:31:57 UTC (rev= 6384) +++ branches/VALGRIND_3_2_BRANCH/Makefile.am 2006-12-07 15:34:04 UTC (rev= 6385) @@ -67,7 +67,7 @@ valgrind.spec.in valgrind.pc.in \ Makefile.all.am Makefile.tool.am Makefile.core.am \ Makefile.tool-inplace.am \ - $(VEX_PRIMARY_SOURCES) + $(vex_primary_sources) =20 install-exec-hook: $(mkinstalldirs) $(DESTDIR)$(valdir) @@ -98,7 +98,7 @@ =20 # These list the bits of vex we need to copy into the tarball =20 -VEX_PRIMARY_SOURCES =3D \ +vex_primary_sources =3D \ VEX/HACKING.README \ VEX/LICENSE.README \ VEX/LICENSE.GPL \ |
|
From: <sv...@va...> - 2006-12-07 15:32:08
|
Author: dirk Date: 2006-12-07 15:31:57 +0000 (Thu, 07 Dec 2006) New Revision: 6384 Log: rename as _SOURCES is a reserved keywoard and breaks with newer auto*foo:=20 Makefile.am:110: variable `VEX_PRIMARY_SOURCES' is defined but no program or Makefile.am:110: library has `VEX_PRIMARY' as canonic name (possible typo) Modified: trunk/Makefile.am Modified: trunk/Makefile.am =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/Makefile.am 2006-12-06 18:53:07 UTC (rev 6383) +++ trunk/Makefile.am 2006-12-07 15:31:57 UTC (rev 6384) @@ -76,7 +76,7 @@ valgrind.spec.in valgrind.pc.in \ Makefile.all.am Makefile.tool.am Makefile.core.am \ Makefile.tool-inplace.am \ - $(VEX_PRIMARY_SOURCES) + $(vex_primary_sources) =20 install-exec-hook: $(mkinstalldirs) $(DESTDIR)$(valdir) @@ -107,7 +107,7 @@ =20 # These list the bits of vex we need to copy into the tarball =20 -VEX_PRIMARY_SOURCES =3D \ +vex_primary_sources =3D \ VEX/quote.txt \ VEX/newline.txt \ VEX/HACKING.README \ |
|
From: Bart V. A. <bar...@gm...> - 2006-12-07 13:35:04
|
On 12/7/06, Julian Seward <js...@ac...> wrote: > On Thursday 07 December 2006 10:55, Bart Van Assche wrote: > > http://home.euphonynet.be/bvassche/valgrind/valgrind-6361-core-2006-11-20.p > >atch Note: I'm currently reworking these core changes such that detached > > threads can be supported. > > On a quick look at that, I notice(d before now) your pthread_* function > wrappers are in coregrind/vg_preloaded.c. I would prefer that those > wrappers be placed in a drd-specific its own preload .so, in the same > way that memcheck has its malloc wrappers placed in its own .so, > vgpreload_memcheck-<platform>.so. > > This has two advantages: (1) it avoids forcing all tools to use the pthread > wrappers when they don't need to, which avoids a potentially large performance > loss, and (2) it reduces the amount of drd-specific stuff that the core needs > to know about. In particularly, it ought to be possible to engineer this so > that the core does not have to know anything about the drd-specific client > requests either. Moving the pthread_* function wrappers to a drd-specific preload is no problem. But did you consider the following: - every tool that needs information about thread events (e.g. helgrind or a tool that tracks stack usage of threads) will have to be informed about thread creation and thread termination. - The overhead of having wrappers in vg_preloaded.c for pthread_create() and pthread_join() is relatively small, the impact is only significant for software that creates and stops threads very quickly. The largest performance penalty is for none/tests/manythreads: with --tool=none and without my patch, it completes in 1.60s. With my patch and --tool=none it completes in about 1.63s, or a slowdown of 2%. Maybe I can keep the wrappers for pthread_create()/pthread_join() in vg_preloaded.c, and move the other wrappers to a drd/... file ? Bart. |
|
From: Julian S. <js...@ac...> - 2006-12-07 12:10:50
|
On Thursday 07 December 2006 10:55, Bart Van Assche wrote: > On 12/7/06, Nicholas Nethercote <nj...@cs...> wrote: > > On Thu, 7 Dec 2006, Bart Van Assche wrote: > > > Will it be possible for experimental tools to branch Valgrind's core ? > > > > We hadn't thought of that... I'm not sure how it would be possible. Doesn't sound desirable to me .. will increase the long term maintenance overhead. > http://home.euphonynet.be/bvassche/valgrind/valgrind-6361-core-2006-11-20.p >atch Note: I'm currently reworking these core changes such that detached > threads can be supported. On a quick look at that, I notice(d before now) your pthread_* function wrappers are in coregrind/vg_preloaded.c. I would prefer that those wrappers be placed in a drd-specific its own preload .so, in the same way that memcheck has its malloc wrappers placed in its own .so, vgpreload_memcheck-<platform>.so. This has two advantages: (1) it avoids forcing all tools to use the pthread wrappers when they don't need to, which avoids a potentially large performance loss, and (2) it reduces the amount of drd-specific stuff that the core needs to know about. In particularly, it ought to be possible to engineer this so that the core does not have to know anything about the drd-specific client requests either. J |
|
From: Bart V. A. <bar...@gm...> - 2006-12-07 11:03:01
|
On 12/7/06, Nicholas Nethercote <nj...@cs...> wrote: > On Thu, 7 Dec 2006, Bart Van Assche wrote: > > > Will it be possible for experimental tools to branch Valgrind's core ? > > We hadn't thought of that... I'm not sure how it would be possible. Better > would probably be to try to add whatever features the tool needs to the the > standard core, so long as they're not too dramatic. IIRC we've already > made some core changes for DRD, are there more required? (Sorry if you've > mentioned them before and I've forgotten.) > > Nick The core changes required for drd are substantial -- this is the last published version of the core changes: http://home.euphonynet.be/bvassche/valgrind/valgrind-6361-core-2006-11-20.patch Note: I'm currently reworking these core changes such that detached threads can be supported. Bart. |
|
From: Nicholas N. <nj...@cs...> - 2006-12-07 10:41:05
|
On Thu, 7 Dec 2006, Bart Van Assche wrote: >> Julian and I have been discussing the idea of having an area for >> experimental tools in the Valgrind distribution. It'll probably get >> introduced in release 3.3.0. > > Will it be possible for experimental tools to branch Valgrind's core ? We hadn't thought of that... I'm not sure how it would be possible. Better would probably be to try to add whatever features the tool needs to the the standard core, so long as they're not too dramatic. IIRC we've already made some core changes for DRD, are there more required? (Sorry if you've mentioned them before and I've forgotten.) Nick |
|
From: Bart V. A. <bar...@gm...> - 2006-12-07 07:33:51
|
On 12/6/06, Nicholas Nethercote <nj...@cs...> wrote: > > Julian and I have been discussing the idea of having an area for > experimental tools in the Valgrind distribution. It'll probably get > introduced in release 3.3.0. > > Nick Will it be possible for experimental tools to branch Valgrind's core ? Bart. |
|
From: <js...@ac...> - 2006-12-07 05:03:42
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-12-07 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, 9 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-cycle (stderr) 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/blockfault (stderr) none/tests/fdleak_cmsg (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 Regression test results follow == 249 tests, 8 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/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Dec 7 04:47:20 2006 --- new.short Thu Dec 7 05:03:45 2006 *************** *** 10,12 **** ! == 249 tests, 8 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (stderr) --- 10,13 ---- ! == 250 tests, 9 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) |
|
From: <js...@ac...> - 2006-12-07 04:25:03
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-12-07 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, 12 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/blockfault (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/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-12-07 03:47:22
|
Nightly build on dunsmere ( athlon, Fedora Core 6 ) started at 2006-12-07 03:30:04 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, 8 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (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 Regression test results follow == 251 tests, 7 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/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Dec 7 03:38:45 2006 --- new.short Thu Dec 7 03:47:18 2006 *************** *** 8,10 **** ! == 251 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) --- 8,11 ---- ! == 252 tests, 8 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/leak-cycle (stderr) memcheck/tests/pointer-trace (stderr) |
|
From: Tom H. <th...@cy...> - 2006-12-07 03:32:39
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2006-12-07 03:10: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 == 280 tests, 13 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/pth_detached (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 == 279 tests, 13 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Dec 7 03:22:05 2006 --- new.short Thu Dec 7 03:32:22 2006 *************** *** 8,10 **** ! == 279 tests, 13 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) --- 8,10 ---- ! == 280 tests, 13 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) *************** *** 23,24 **** --- 23,25 ---- none/tests/mremap2 (stdout) + none/tests/pth_detached (stdout) |
|
From: Tom H. <th...@cy...> - 2006-12-07 03:32:31
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-12-07 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/ccl5pD7a.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccl5pD7a.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccl5pD7a.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccl5pD7a.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccl5pD7a.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccl5pD7a.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccl5pD7a.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccl5pD7a.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.5008/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.5008/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.5008/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.5008/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.5008/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/ccZw63Ao.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccZw63Ao.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccZw63Ao.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccZw63Ao.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccZw63Ao.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccZw63Ao.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccZw63Ao.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccZw63Ao.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.5008/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.5008/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.5008/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.5008/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.5008/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Dec 7 03:23:59 2006 --- new.short Thu Dec 7 03:32:14 2006 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccZw63Ao.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccZw63Ao.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccZw63Ao.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccZw63Ao.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccZw63Ao.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccZw63Ao.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccZw63Ao.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccZw63Ao.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/ccl5pD7a.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccl5pD7a.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccl5pD7a.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccl5pD7a.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccl5pD7a.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccl5pD7a.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccl5pD7a.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccl5pD7a.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2006-12-07 03:26:36
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2006-12-07 03:05: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 == 280 tests, 14 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) 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/blockfault (stderr) none/tests/fdleak_cmsg (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 Regression test results follow == 279 tests, 14 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) 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/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Dec 7 03:15:15 2006 --- new.short Thu Dec 7 03:26:19 2006 *************** *** 8,10 **** ! == 279 tests, 14 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) --- 8,10 ---- ! == 280 tests, 14 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-12-07 03:20:50
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-12-07 03:00:04 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, 15 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) 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/blockfault (stderr) none/tests/fdleak_cmsg (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 Regression test results follow == 281 tests, 15 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) 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/blockfault (stderr) none/tests/fdleak_cmsg (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Dec 7 03:09:19 2006 --- new.short Thu Dec 7 03:20:22 2006 *************** *** 8,10 **** ! == 281 tests, 15 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) --- 8,10 ---- ! == 282 tests, 15 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-pool-0 (stderr) |
|
From: <js...@ac...> - 2006-12-07 01:16:42
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2006-12-07 02:00:01 CET 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 == 221 tests, 14 stderr failures, 4 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) none/tests/blockfault (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-int (stdout) none/tests/ppc64/jm-int (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 == 220 tests, 14 stderr failures, 4 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-pool-0 (stderr) memcheck/tests/leak-pool-1 (stderr) memcheck/tests/leak-pool-2 (stderr) memcheck/tests/leak-pool-3 (stderr) memcheck/tests/leak-pool-4 (stderr) memcheck/tests/leak-pool-5 (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) none/tests/blockfault (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-int (stdout) none/tests/ppc64/jm-int (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Dec 7 02:08:19 2006 --- new.short Thu Dec 7 02:16:39 2006 *************** *** 8,10 **** ! == 220 tests, 14 stderr failures, 4 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) --- 8,10 ---- ! == 221 tests, 14 stderr failures, 4 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) |