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
(16) |
3
(7) |
|
4
(7) |
5
(9) |
6
(8) |
7
(10) |
8
(16) |
9
(15) |
10
(9) |
|
11
(11) |
12
(13) |
13
(8) |
14
(8) |
15
(10) |
16
(25) |
17
(7) |
|
18
(7) |
19
(13) |
20
(10) |
21
(14) |
22
(11) |
23
(12) |
24
(8) |
|
25
(19) |
26
(10) |
27
(16) |
28
(13) |
|
|
|
|
From: Nicholas N. <nj...@cs...> - 2007-02-19 21:49:07
|
On Mon, 19 Feb 2007, Tom Hughes wrote: >> * Only mark output structs as written if the syscall succeeded. > > This should not be needed - the POST handler is only called if the > system call succeeds (or if the SfPostOnFail flag has been set by > the PRE handler). So the "if (FAILURE)" lines aren't necessary? The rest seems good -- if you agree, Tom, could you commit it? Thanks. Nick |
|
From: Tom H. <to...@co...> - 2007-02-19 14:06:39
|
In message <BAY...@ph...l>
Magnus Vesterlund <mag...@ho...> wrote:
> * Only mark output structs as written if the syscall succeeded.
This should not be needed - the POST handler is only called if the
system call succeeds (or if the SfPostOnFail flag has been set by
the PRE handler).
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Magnus V. <mag...@ho...> - 2007-02-19 13:14:38
|
Hi!
Here is a patch against trunk that improves ptrace support on x86 and amd64:
* Only mark output structs as written if the syscall succeeded.
* Adds support for PTRACE_GETEVENTMSG, PTRACE_GETSIGINFO and
PTRACE_SETSIGINFO.
/Magnus
Index: include/vki/vki-linux.h
===================================================================
--- include/vki/vki-linux.h (revision 6605)
+++ include/vki/vki-linux.h (working copy)
@@ -2103,6 +2103,14 @@
#define VKI_PTRACE_DETACH 0x11
//----------------------------------------------------------------------
+// From linux-2.6.20/include/linux/ptrace.h
+//----------------------------------------------------------------------
+
+#define VKI_PTRACE_GETEVENTMSG 0x4201
+#define VKI_PTRACE_GETSIGINFO 0x4202
+#define VKI_PTRACE_SETSIGINFO 0x4203
+
+//----------------------------------------------------------------------
// From linux-2.6.14/include/sound/asound.h
//----------------------------------------------------------------------
Index: coregrind/m_syswrap/syswrap-amd64-linux.c
===================================================================
--- coregrind/m_syswrap/syswrap-amd64-linux.c (revision 6605)
+++ coregrind/m_syswrap/syswrap-amd64-linux.c (working copy)
@@ -517,7 +517,11 @@
}
// Parts of this are amd64-specific, but the *PEEK* cases are generic.
-// XXX: Why is the memory pointed to by ARG3 never checked?
+//
+// ARG3 is only used for pointers into the traced process's address space
and
+// for offsets into the traced process's struct user_regs_struct. It is
never a
+// pointer into this process's memory space, and we should therefore not
check
+// anything it points to.
PRE(sys_ptrace)
{
PRINT("sys_ptrace ( %d, %d, %p, %p )", ARG1,ARG2,ARG3,ARG4);
@@ -546,6 +550,15 @@
PRE_MEM_READ( "ptrace(setfpregs)", ARG4,
sizeof (struct vki_user_i387_struct));
break;
+ case VKI_PTRACE_GETEVENTMSG:
+ PRE_MEM_WRITE( "ptrace(geteventmsg)", ARG4, sizeof(unsigned long));
+ break;
+ case VKI_PTRACE_GETSIGINFO:
+ PRE_MEM_WRITE( "ptrace(getsiginfo)", ARG4, sizeof(vki_siginfo_t));
+ break;
+ case VKI_PTRACE_SETSIGINFO:
+ PRE_MEM_READ( "ptrace(setsiginfo)", ARG4, sizeof(vki_siginfo_t));
+ break;
default:
break;
}
@@ -553,6 +566,9 @@
POST(sys_ptrace)
{
+ if (FAILURE)
+ return;
+
switch (ARG1) {
case VKI_PTRACE_PEEKTEXT:
case VKI_PTRACE_PEEKDATA:
@@ -565,6 +581,14 @@
case VKI_PTRACE_GETFPREGS:
POST_MEM_WRITE( ARG4, sizeof (struct vki_user_i387_struct));
break;
+ case VKI_PTRACE_GETEVENTMSG:
+ POST_MEM_WRITE( ARG4, sizeof(unsigned long));
+ break;
+ case VKI_PTRACE_GETSIGINFO:
+ /* XXX: This is a simplification. Different parts of the siginfo_t
are
+ valid depending on the type of signal, see "man sigaction".*/
+ POST_MEM_WRITE( ARG4, sizeof(vki_siginfo_t));
+ break;
default:
break;
}
Index: coregrind/m_syswrap/syswrap-x86-linux.c
===================================================================
--- coregrind/m_syswrap/syswrap-x86-linux.c (revision 6605)
+++ coregrind/m_syswrap/syswrap-x86-linux.c (working copy)
@@ -1042,7 +1042,11 @@
}
// Parts of this are x86-specific, but the *PEEK* cases are generic.
-// XXX: Why is the memory pointed to by ARG3 never checked?
+//
+// ARG3 is only used for pointers into the traced process's address space
and
+// for offsets into the traced process's struct user_regs_struct. It is
never a
+// pointer into this process's memory space, and we should therefore not
check
+// anything it points to.
PRE(sys_ptrace)
{
PRINT("sys_ptrace ( %d, %d, %p, %p )", ARG1,ARG2,ARG3,ARG4);
@@ -1079,6 +1083,15 @@
PRE_MEM_READ( "ptrace(setfpxregs)", ARG4,
sizeof(struct vki_user_fxsr_struct) );
break;
+ case VKI_PTRACE_GETEVENTMSG:
+ PRE_MEM_WRITE( "ptrace(geteventmsg)", ARG4, sizeof(unsigned long));
+ break;
+ case VKI_PTRACE_GETSIGINFO:
+ PRE_MEM_WRITE( "ptrace(getsiginfo)", ARG4, sizeof(vki_siginfo_t));
+ break;
+ case VKI_PTRACE_SETSIGINFO:
+ PRE_MEM_READ( "ptrace(setsiginfo)", ARG4, sizeof(vki_siginfo_t));
+ break;
default:
break;
}
@@ -1086,6 +1099,9 @@
POST(sys_ptrace)
{
+ if (FAILURE)
+ return;
+
switch (ARG1) {
case VKI_PTRACE_PEEKTEXT:
case VKI_PTRACE_PEEKDATA:
@@ -1101,6 +1117,14 @@
case VKI_PTRACE_GETFPXREGS:
POST_MEM_WRITE( ARG4, sizeof(struct vki_user_fxsr_struct) );
break;
+ case VKI_PTRACE_GETEVENTMSG:
+ POST_MEM_WRITE( ARG4, sizeof(unsigned long));
+ break;
+ case VKI_PTRACE_GETSIGINFO:
+ /* XXX: This is a simplification. Different parts of the siginfo_t
are
+ valid depending on the type of signal, see "man sigaction".*/
+ POST_MEM_WRITE( ARG4, sizeof(vki_siginfo_t));
+ break;
default:
break;
}
|
|
From: <sv...@va...> - 2007-02-19 11:51:20
|
Author: njn Date: 2007-02-19 11:51:16 +0000 (Mon, 19 Feb 2007) New Revision: 6605 Log: Improved things. Now detecting origins of undefined values on the stack, albeit with stack traces containing only one entry (but that's way better than zero entries). Creating the necessary ExeContexts at instrumentation-time, as opposed to the run-time ones for heap blocks. Preliminary experiments with SPEC show that it doesn't cause much more slow-down than what we've already got, eg. usually around the 3--8% range, although a couple are more like 25%. This required adding an alternative way for tools to instrument SP updates, one that it more powerful than the new_mem_stack/die_mem_stack events. This new mechanism is powerful but not particularly elegant. I also turned off the larger new_mem_stack/die_mem_stack cases (112, 128, 144, 160 bytes) because I don't think they make any difference. Added: branches/ORIGIN_TRACKING/include/pub_tool_stacks.h branches/ORIGIN_TRACKING/include/pub_tool_translate.h Modified: branches/ORIGIN_TRACKING/coregrind/m_execontext.c branches/ORIGIN_TRACKING/coregrind/m_stacks.c branches/ORIGIN_TRACKING/coregrind/m_tooliface.c branches/ORIGIN_TRACKING/coregrind/m_translate.c branches/ORIGIN_TRACKING/coregrind/pub_core_stacks.h branches/ORIGIN_TRACKING/coregrind/pub_core_tooliface.h branches/ORIGIN_TRACKING/coregrind/pub_core_translate.h branches/ORIGIN_TRACKING/include/pub_tool_execontext.h branches/ORIGIN_TRACKING/include/pub_tool_tooliface.h branches/ORIGIN_TRACKING/memcheck/mc_include.h branches/ORIGIN_TRACKING/memcheck/mc_main.c branches/ORIGIN_TRACKING/memcheck/mc_translate.c branches/ORIGIN_TRACKING/memcheck/tests/badloop.stderr.exp branches/ORIGIN_TRACKING/memcheck/tests/inits.stderr.exp branches/ORIGIN_TRACKING/memcheck/tests/origin-no.c branches/ORIGIN_TRACKING/memcheck/tests/origin-not-quite.c branches/ORIGIN_TRACKING/memcheck/tests/origin-not-quite.stderr.exp branches/ORIGIN_TRACKING/memcheck/tests/origin-yes.c branches/ORIGIN_TRACKING/memcheck/tests/origin-yes.stderr.exp [... diff too large to include ...] |
|
From: <js...@ac...> - 2007-02-19 09:36:19
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2007-02-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 == 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-02-19 05:29:17
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2007-02-19 04:55: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 == 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) ================================================= == 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 == 254 tests, 6 stderr failures, 2 stdout failures, 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) none/tests/pth_detached (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Mon Feb 19 05:12:23 2007 --- new.short Mon Feb 19 05:29:47 2007 *************** *** 10,12 **** ! == 254 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) --- 10,12 ---- ! == 254 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (stderr) *************** *** 18,20 **** none/tests/mremap2 (stdout) - none/tests/pth_detached (stdout) --- 18,19 ---- |
|
From: <sv...@va...> - 2007-02-19 04:16:12
|
Author: njn
Date: 2007-02-19 04:16:09 +0000 (Mon, 19 Feb 2007)
New Revision: 6604
Log:
comment
Modified:
trunk/vg-in-place
Modified: trunk/vg-in-place
===================================================================
--- trunk/vg-in-place 2007-02-19 04:09:24 UTC (rev 6603)
+++ trunk/vg-in-place 2007-02-19 04:16:09 UTC (rev 6604)
@@ -1,6 +1,8 @@
# This ensures it works when invoked from any directory.
d=`dirname $0`
+# We set both VALGRIND_LIB and VALGRIND_LIB_INNER to handle normal and
+# 'inner' builds.
VALGRIND_LIB=$d/.in_place \
VALGRIND_LIB_INNER=$d/.in_place \
$d/coregrind/valgrind "$@"
|
|
From: Tom H. <th...@cy...> - 2007-02-19 04:11:44
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-02-19 03:00: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 == 290 tests, 6 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/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/tls (stdout) |
|
From: <sv...@va...> - 2007-02-19 04:09:27
|
Author: njn Date: 2007-02-19 04:09:24 +0000 (Mon, 19 Feb 2007) New Revision: 6603 Log: Add a script to make running in-place simpler. Added: trunk/vg-in-place Modified: trunk/README_DEVELOPERS Modified: trunk/README_DEVELOPERS =================================================================== --- trunk/README_DEVELOPERS 2007-02-16 21:57:27 UTC (rev 6602) +++ trunk/README_DEVELOPERS 2007-02-19 04:09:24 UTC (rev 6603) @@ -10,6 +10,8 @@ This allows you to compile and run with "make" instead of "make install", saving you time. +Or, you can use the 'vg-in-place' script which does that for you. + I recommend compiling with "make --quiet" to further reduce the amount of output spewed out during compilation, letting you actually see any errors, warnings, etc. Added: trunk/vg-in-place =================================================================== --- trunk/vg-in-place (rev 0) +++ trunk/vg-in-place 2007-02-19 04:09:24 UTC (rev 6603) @@ -0,0 +1,7 @@ +# This ensures it works when invoked from any directory. +d=`dirname $0` + +VALGRIND_LIB=$d/.in_place \ + VALGRIND_LIB_INNER=$d/.in_place \ + $d/coregrind/valgrind "$@" + Property changes on: trunk/vg-in-place ___________________________________________________________________ Name: svn:executable + * |
|
From: Tom H. <th...@cy...> - 2007-02-19 03:23:19
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2007-02-19 03:10:08 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 == 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) |
|
From: Tom H. <th...@cy...> - 2007-02-19 03:22:52
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-02-19 03:15:01 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/ccT7Moyv.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccT7Moyv.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccT7Moyv.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccT7Moyv.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccT7Moyv.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccT7Moyv.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccT7Moyv.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccT7Moyv.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.13599/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.13599/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.13599/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.13599/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.13599/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/cc5DbbQd.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc5DbbQd.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc5DbbQd.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc5DbbQd.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc5DbbQd.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc5DbbQd.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc5DbbQd.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/cc5DbbQd.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.13599/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.13599/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.13599/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.13599/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.13599/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Mon Feb 19 03:18:48 2007 --- new.short Mon Feb 19 03:22:44 2007 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/cc5DbbQd.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc5DbbQd.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc5DbbQd.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc5DbbQd.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc5DbbQd.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc5DbbQd.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc5DbbQd.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/cc5DbbQd.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/ccT7Moyv.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccT7Moyv.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccT7Moyv.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccT7Moyv.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccT7Moyv.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccT7Moyv.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccT7Moyv.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccT7Moyv.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Tom H. <th...@cy...> - 2007-02-19 03:18:58
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2007-02-19 03:05:06 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 == 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) |
|
From: <js...@ac...> - 2007-02-19 02:37:36
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-02-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 == 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) |