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
(14) |
2
(8) |
3
(7) |
|
4
(7) |
5
(7) |
6
(6) |
7
(11) |
8
(10) |
9
(14) |
10
(10) |
|
11
(13) |
12
(15) |
13
(6) |
14
(8) |
15
(6) |
16
(6) |
17
(6) |
|
18
(6) |
19
(11) |
20
(15) |
21
(14) |
22
(11) |
23
(7) |
24
(17) |
|
25
(14) |
26
(28) |
27
(21) |
28
(23) |
29
(21) |
30
(17) |
31
(8) |
|
From: Nicholas N. <nj...@cs...> - 2007-03-01 21:32:28
|
On Thu, 1 Mar 2007, Craig, Rocky wrote: > But seriously, I want to understand how hard it would be to get > this running on ia64. We have a lot of code dying to be examined > and I'm interested in starting the porting effort. > > Is it harder than any other architecture? > > Have others tried and given up? > > Any other "top of your head" warnings/ideas/pointers/advice for > someone who really doesn't know enough NOT to ask :-) Julian has given this some consideration. My understanding is that IA64 would be extremely difficult, partly because it's VLIW, and partly because of some other weird IA64 features. I can't remember what they are now. Nick |
|
From: Craig, R. <roc...@hp...> - 2007-03-01 19:44:57
|
Greetings, I've been over the website docs and mailing list archives=20 (including the survey) and come away with two themes: 1. Porting valgrind (in particular, memcheck) would be very hard 2. It's only a 5% interest/usage case so we don't care Coming from the HP Integrity Server part of the cosmos, I have more than a 5% interest :-) But seriously, I want to understand how hard it would be to get this running on ia64. We have a lot of code dying to be examined and I'm interested in starting the porting effort. Is it harder than any other architecture? Have others tried and given up? Any other "top of your head" warnings/ideas/pointers/advice for someone who really doesn't know enough NOT to ask :-) Thanks, Rocky Craig Open Source and Linux Operation Integrity Server Manageability Hewlett-Packard, Fort Collins, Colorado |
|
From: Bart V. A. <bar...@gm...> - 2007-03-01 18:58:51
|
On 2/27/07, Nicholas Nethercote <nj...@cs...> wrote: > On Tue, 27 Feb 2007, Bart Van Assche wrote: > > > - Started optimizing the bitmap implementation in drd -- drd now works > > several times faster for clients with 10 threads or more. More work > > has to be done in this area however. (Only bm_clear() and > > bm_has_access() have been optimized. According to cachegrind, > > VG_(OSet_Next)() is now the function that consumes most CPU cycles.) > > Cachegrind doesn't tell you cycles, only instructions and cache misses. > Often they correlate to cycles pretty well but not always. > > If OSet is too slow, you could try using VgHashTable (see > pub_tool_hashtable.h). It has a similar interface and so you might be able > to switch over easily. It's faster in some cases, especially for iteration. > Or, you could try to reduce the number of times you iterate over the data > structure :) Good suggestion. But I'm not sure which hash size to choose ? There are a lot of bitmaps allocated during program run, some small, some large. I'll consider this anyway as an option when I continue optimizing. Bart. |
|
From: Bart V. A. <bar...@gm...> - 2007-03-01 18:42:51
|
One of drd's regression tests still fails on AMD64 because
VG_(find_seginfo)() fails for BSS symbols on AMD64. Are there any
plans to fix this problem ?
bart@athlon:~/software/valgrind-inner> perl tests/vg_regtest drd
-- Running tests in drd/tests -----------------------------------------
fp_race: valgrind ./fp_race
*** fp_race failed (stderr) ***
fp_race2: valgrind ./fp_race -m
pth_cond_race: valgrind ./pth_cond_race
pth_cond_race2: valgrind ./pth_cond_race -m
pth_detached: valgrind ./pth_detached 1 1
pth_detached2: valgrind ./pth_detached 10 10
-- Finished tests in drd/tests -----------------------------------------
---------- Forwarded message ----------
From: Bart Van Assche <bar...@gm...>
Date: Jan 13, 2007 9:33 PM
Subject: VG_(find_seginfo)() on 64-bit platforms
To: Valgrind Developers <val...@li...>
While porting drd from x86 to amd64, I noticed that while
VG_(find_seginfo)() works on x86 for symbols in a BSS section, it
doesn't return any info on amd64. With the test program
drd/tests/fp_race I get the following output on x86:
...
Allocation context: s_d3 (offset 0, size 8) in fp_race, NONE:BSS
...
But this is what I get on amd64:
...
Allocation context: unknown
...
The cause of this difference in output is that
VG_(find_seginfo)(&s_d3) returns a null pointer on amd64. There is
symbol information for s_d3 in the fp_race executable however:
$ readelf -a drd/tests/fp_race|grep s_d3
66: 00000000006020f8 8 OBJECT LOCAL DEFAULT 26 s_d3
$ objdump -x drd/tests/fp_race|grep s_d3
00000000006020f8 l O .bss 0000000000000008 s_d3
$ nm drd/tests/fp_race|grep s_d3
00000000006020f8 b s_d3
Is the above output enough to explain why VG_(find_seginfo)(&s_d3) ==
0 on amd64 ? Are there any known issues regarding to looking up symbol
information in BSS sections on amd64 ?
Bart.
|
|
From: <sv...@va...> - 2007-03-01 18:42:11
|
Author: sewardj
Date: 2007-03-01 18:42:07 +0000 (Thu, 01 Mar 2007)
New Revision: 1737
Log:
Handle the (bizarre) no-op "26 2E 64 65 90 %es:%cs:%fs:%gs:nop". This
makes it possible to run Sun's JVM 1.5.0 on Valgrind.
Modified:
trunk/priv/guest-x86/toIR.c
Modified: trunk/priv/guest-x86/toIR.c
===================================================================
--- trunk/priv/guest-x86/toIR.c 2007-02-28 23:31:42 UTC (rev 1736)
+++ trunk/priv/guest-x86/toIR.c 2007-03-01 18:42:07 UTC (rev 1737)
@@ -7272,6 +7272,18 @@
switch (getIByte(delta)) {
case 0x3E: /* %DS: */
case 0x26: /* %ES: */
+ /* Sun's JVM 1.5.0 uses the following as a NOP:
+ 26 2E 64 65 90 %es:%cs:%fs:%gs:nop */
+ {
+ UChar* code = (UChar*)(guest_code + delta);
+ if (code[0] == 0x26 && code[1] == 0x2E && code[2] == 0x64
+ && code[3] == 0x65 && code[4] == 0x90) {
+ DIP("%%es:%%cs:%%fs:%%gs:nop\n");
+ delta += 5;
+ goto decode_success;
+ }
+ /* else fall through */
+ }
case 0x64: /* %FS: */
case 0x65: /* %GS: */
sorb = getIByte(delta); delta++;
|
|
From: Bart V. A. <bar...@gm...> - 2007-03-01 17:50:10
|
On 3/1/07, xiaoming gu <xia...@gm...> wrote: > Hi, all. I write a new tool based on valgrind and want to test itself, but > when I did the profiling there was an error message: > valgrind: You cannot run './valgrind' directly. > valgrind: You should use $prefix/bin/valgrind. > Then I specified the profiled valgrind using full path and it didn't work. > > Does anybody do something like this before? Please give me some > details. Thanks a lot. Have a look at the README_DEVELOPERS document in the source distribution -- this document explains how to profile a valgrind tool with cachegrind or callgrind. Regards, Bart Van Assche. |
|
From: xiaoming g. <xia...@gm...> - 2007-03-01 14:18:26
|
<val...@va...>Hi, all. I write a new tool based on valgrind and
want to test itself, but
when I did the profiling there was an error message:
valgrind: You cannot run './valgrind' directly.
valgrind: You should use $prefix/bin/valgrind.
Then I specified the profiled valgrind using full path and it didn't work.
Does anybody do something like this before? Please give me some
details. Thanks a lot.
Xiaoming
|
|
From: <js...@ac...> - 2007-03-01 10:16:01
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2007-03-01 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 == 219 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...> - 2007-03-01 05:31:27
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2007-03-01 04:55: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 == 254 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. <th...@cy...> - 2007-03-01 03:24:17
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-03-01 03:15:02 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/cc64Bwyp.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc64Bwyp.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc64Bwyp.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc64Bwyp.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc64Bwyp.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc64Bwyp.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc64Bwyp.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc64Bwyp.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/vgtest/2007-03-01/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/vgtest/2007-03-01/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/vgtest/2007-03-01/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/vgtest/2007-03-01/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/vgtest/2007-03-01/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/cce5wuv6.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cce5wuv6.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cce5wuv6.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cce5wuv6.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cce5wuv6.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cce5wuv6.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cce5wuv6.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cce5wuv6.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/vgtest/2007-03-01/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/vgtest/2007-03-01/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/vgtest/2007-03-01/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/vgtest/2007-03-01/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/vgtest/2007-03-01/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Mar 1 03:19:38 2007 --- new.short Thu Mar 1 03:24:05 2007 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/cce5wuv6.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cce5wuv6.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cce5wuv6.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cce5wuv6.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cce5wuv6.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cce5wuv6.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cce5wuv6.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cce5wuv6.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/cc64Bwyp.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc64Bwyp.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc64Bwyp.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc64Bwyp.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc64Bwyp.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc64Bwyp.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc64Bwyp.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc64Bwyp.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2007-03-01 03:23:53
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2007-03-01 03:10: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 == 289 tests, 5 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/amd64/defcfaexpr (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (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 == 288 tests, 4 stderr failures, 2 stdout failures, 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) none/tests/pth_detached (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Mar 1 03:17:04 2007 --- new.short Thu Mar 1 03:23:45 2007 *************** *** 8,10 **** ! == 288 tests, 4 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) --- 8,11 ---- ! == 289 tests, 5 stderr failures, 2 stdout failures, 0 posttest failures == ! memcheck/tests/amd64/defcfaexpr (stderr) memcheck/tests/pointer-trace (stderr) |
|
From: Tom H. <th...@cy...> - 2007-03-01 03:18:49
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2007-03-01 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 == 289 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/amd64/defcfaexpr (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (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 == 288 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) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Mar 1 03:12:36 2007 --- new.short Thu Mar 1 03:18:41 2007 *************** *** 8,10 **** ! == 288 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) --- 8,11 ---- ! == 289 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/amd64/defcfaexpr (stderr) memcheck/tests/pointer-trace (stderr) |
|
From: Tom H. <th...@cy...> - 2007-03-01 03:14:11
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-03-01 03:00:03 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 == 291 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/amd64/defcfaexpr (stderr) 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 Regression test results follow == 290 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) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Mar 1 03:08:20 2007 --- new.short Thu Mar 1 03:14:03 2007 *************** *** 8,10 **** ! == 290 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) --- 8,11 ---- ! == 291 tests, 7 stderr failures, 1 stdout failure, 0 posttest failures == ! memcheck/tests/amd64/defcfaexpr (stderr) memcheck/tests/pointer-trace (stderr) |
|
From: <js...@ac...> - 2007-03-01 01:16:41
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-03-01 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 == 225 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) |