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
(32) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
1
(29) |
2
(23) |
3
(17) |
|
4
(19) |
5
(7) |
6
(11) |
7
(8) |
8
(6) |
9
(12) |
10
(23) |
|
11
(16) |
12
(21) |
13
(27) |
14
(35) |
15
(17) |
16
(6) |
17
(11) |
|
18
(13) |
19
(7) |
20
(12) |
21
(11) |
22
(9) |
23
|
24
(8) |
|
25
(15) |
26
(9) |
27
(14) |
28
(17) |
29
(41) |
30
(17) |
31
(15) |
|
From: <sv...@va...> - 2008-05-28 11:06:02
|
Author: sewardj
Date: 2008-05-28 12:06:08 +0100 (Wed, 28 May 2008)
New Revision: 8138
Log:
Tidy up timerfd wrapper stuff a bit:
* make linux_kernel_2_6_22 return Bool
* linux_kernel_2_6_22: don't assert if /proc/sys/kernel/osrelease
can't be opened
* PRE(sys_timerfd_create), PRE(sys_signalfd):
use %ld for Word arguments, and use house types
Modified:
trunk/coregrind/m_syswrap/syswrap-linux.c
Modified: trunk/coregrind/m_syswrap/syswrap-linux.c
===================================================================
--- trunk/coregrind/m_syswrap/syswrap-linux.c 2008-05-28 08:38:18 UTC (rev 8137)
+++ trunk/coregrind/m_syswrap/syswrap-linux.c 2008-05-28 11:06:08 UTC (rev 8138)
@@ -1713,48 +1713,48 @@
See also /usr/src/linux/fs/timerfd.c for the implementation.
------------------------------------------------------------------ */
-static int linux_kernel_2_6_22(void)
+/* Returns True if running on 2.6.22, else False (or False if
+ cannot be determined). */
+static Bool linux_kernel_2_6_22(void)
{
- static int result = -1;
- Int fd, read;
- char release[64];
- SysRes res;
+ static Int result = -1;
+ Int fd, read;
+ HChar release[64];
+ SysRes res;
- if (result == -1)
- {
- res = VG_(open)("/proc/sys/kernel/osrelease", 0, 0);
- vg_assert(! res.isError);
- fd = res.res;
- read = VG_(read)(fd, release, sizeof(release) - 1);
- vg_assert(read >= 0);
- release[read] = 0;
- VG_(close)(fd);
- //VG_(printf)("kernel release = %s\n", release);
- result = (VG_(strncmp)(release, "2.6.22", 6) == 0
- && (release[6] < '0' || release[6] > '9'));
- }
- return result;
+ if (result == -1) {
+ res = VG_(open)("/proc/sys/kernel/osrelease", 0, 0);
+ if (res.isError)
+ return False;
+ fd = res.res;
+ read = VG_(read)(fd, release, sizeof(release) - 1);
+ vg_assert(read >= 0);
+ release[read] = 0;
+ VG_(close)(fd);
+ //VG_(printf)("kernel release = %s\n", release);
+ result = (VG_(strncmp)(release, "2.6.22", 6) == 0
+ && (release[6] < '0' || release[6] > '9'));
+ }
+ vg_assert(result == 0 || result == 1);
+ return result == 1;
}
PRE(sys_timerfd_create)
{
- if (linux_kernel_2_6_22())
- {
+ if (linux_kernel_2_6_22()) {
/* 2.6.22 kernel: timerfd system call. */
- PRINT("sys_timerfd ( %d, %d, %p )", ARG1, ARG2, ARG3);
+ PRINT("sys_timerfd ( %ld, %ld, %p )", ARG1, ARG2, ARG3);
PRE_REG_READ3(long, "sys_timerfd",
int, fd, int, clockid, const struct itimerspec *, tmr);
PRE_MEM_READ("timerfd(tmr)", ARG3,
sizeof(struct vki_itimerspec) );
- if ((int)ARG1 != -1 && !ML_(fd_allowed)(ARG1, "timerfd", tid, False))
+ if ((Word)ARG1 != -1L && !ML_(fd_allowed)(ARG1, "timerfd", tid, False))
SET_STATUS_Failure( VKI_EBADF );
- }
- else
- {
+ } else {
/* 2.6.24 and later kernels: timerfd_create system call. */
- PRINT("sys_timerfd_create (%d, %d )", ARG1, ARG2);
- PRE_REG_READ2(long, "timerfd_create", int, clockid, int, flags);
- }
+ PRINT("sys_timerfd_create (%ld, %ld )", ARG1, ARG2);
+ PRE_REG_READ2(long, "timerfd_create", int, clockid, int, flags);
+ }
}
POST(sys_timerfd_create)
{
@@ -2377,7 +2377,7 @@
PRE(sys_signalfd)
{
- PRINT("sys_signalfd ( %d, %p, %llu )", ARG1, ARG2, (ULong) ARG3);
+ PRINT("sys_signalfd ( %ld, %p, %llu )", ARG1, ARG2, (ULong) ARG3);
PRE_REG_READ3(long, "sys_signalfd",
int, fd, vki_sigset_t *, sigmask, vki_size_t, sigsetsize);
PRE_MEM_READ( "signalfd(sigmask)", ARG2, sizeof(vki_sigset_t) );
|
|
From: <sv...@va...> - 2008-05-28 09:40:26
|
Author: sewardj
Date: 2008-05-28 10:40:29 +0100 (Wed, 28 May 2008)
New Revision: 1850
Log:
Fix a couple of longstanding enum inconsistencies discovered by
Florian Krohm's static checker.
Modified:
trunk/priv/host-amd64/isel.c
trunk/priv/host-x86/isel.c
Modified: trunk/priv/host-amd64/isel.c
===================================================================
--- trunk/priv/host-amd64/isel.c 2008-05-13 21:32:01 UTC (rev 1849)
+++ trunk/priv/host-amd64/isel.c 2008-05-28 09:40:29 UTC (rev 1850)
@@ -1968,7 +1968,7 @@
switch (ri->tag) {
case Ari_Imm:
return ri;
- case Armi_Reg:
+ case Ari_Reg:
vassert(hregClass(ri->Ari.Reg.reg) == HRcInt64);
vassert(hregIsVirtual(ri->Ari.Reg.reg));
return ri;
Modified: trunk/priv/host-x86/isel.c
===================================================================
--- trunk/priv/host-x86/isel.c 2008-05-13 21:32:01 UTC (rev 1849)
+++ trunk/priv/host-x86/isel.c 2008-05-28 09:40:29 UTC (rev 1850)
@@ -1557,7 +1557,7 @@
switch (ri->tag) {
case Xri_Imm:
return ri;
- case Xrmi_Reg:
+ case Xri_Reg:
vassert(hregClass(ri->Xri.Reg.reg) == HRcInt32);
vassert(hregIsVirtual(ri->Xri.Reg.reg));
return ri;
|
|
From: <sv...@va...> - 2008-05-28 08:38:13
|
Author: bart
Date: 2008-05-28 09:38:18 +0100 (Wed, 28 May 2008)
New Revision: 8137
Log:
Several reader-writer lock related fixes.
Modified:
trunk/exp-drd/drd_rwlock.c
Modified: trunk/exp-drd/drd_rwlock.c
===================================================================
--- trunk/exp-drd/drd_rwlock.c 2008-05-28 07:09:54 UTC (rev 8136)
+++ trunk/exp-drd/drd_rwlock.c 2008-05-28 08:38:18 UTC (rev 8137)
@@ -85,7 +85,7 @@
struct rwlock_thread_info* q;
VG_(OSetGen_ResetIter)(p->thread_info);
- for ( ; (q = VG_(OSetGen_Next)(p->thread_info)); q++)
+ for ( ; (q = VG_(OSetGen_Next)(p->thread_info)) != 0; )
{
return q->reader_nesting_count > 0;
}
@@ -97,7 +97,7 @@
struct rwlock_thread_info* q;
VG_(OSetGen_ResetIter)(p->thread_info);
- for ( ; (q = VG_(OSetGen_Next)(p->thread_info)); q++)
+ for ( ; (q = VG_(OSetGen_Next)(p->thread_info)) != 0; )
{
return q->writer_nesting_count > 0;
}
@@ -213,7 +213,7 @@
}
VG_(OSetGen_ResetIter)(p->thread_info);
- for ( ; (q = VG_(OSetGen_Next)(p->thread_info)); q++)
+ for ( ; (q = VG_(OSetGen_Next)(p->thread_info)) != 0; )
{
sg_put(q->last_unlock_segment);
}
@@ -466,10 +466,10 @@
{
const DrdThreadId drd_tid = thread_get_running_tid();
const ThreadId vg_tid = VG_(get_running_tid)();
- struct rwlock_info* const p = rwlock_get(rwlock);
+ struct rwlock_info* p;
struct rwlock_thread_info* q;
- if (s_trace_rwlock && p != 0)
+ if (s_trace_rwlock)
{
VG_(message)(Vg_UserMsg,
"[%d/%d] rwlock_unlock 0x%lx",
@@ -478,8 +478,19 @@
rwlock);
}
- if (p == 0 || ! rwlock_is_locked_by(p, drd_tid))
+ p = rwlock_get(rwlock);
+ if (p == 0)
{
+ GenericErrInfo GEI;
+ VG_(maybe_record_error)(VG_(get_running_tid)(),
+ GenericErr,
+ VG_(get_IP)(VG_(get_running_tid)()),
+ "Not a reader-writer lock",
+ &GEI);
+ return;
+ }
+ if (! rwlock_is_locked_by(p, drd_tid))
+ {
RwlockErrInfo REI = { p->a1 };
VG_(maybe_record_error)(vg_tid,
RwlockErr,
@@ -488,7 +499,6 @@
&REI);
return;
}
- tl_assert(p);
q = lookup_or_insert_node(p->thread_info, drd_tid);
tl_assert(q);
if (q->reader_nesting_count > 0)
|
|
From: Andrei S. <and...@gm...> - 2008-05-28 08:06:35
|
I suspected that. However, I have no idea how and what I must modify and I would really appreciate some hints. On Wed, May 28, 2008 at 10:56 AM, Nicholas Nethercote < nj...@cs...> wrote: > Massif tracks deallocations, but you're right that it doesn't really say > anything about them, or about allocation lifetimes. > > You could definitely track object lifetimes with a Valgrind tool, and > Massif might be a good place to start because it has a lot of > allocation-tracking infrastructure, but I expect you'd need to make > substantial modifications to it. > > Nick > -- Andrei Soare |
|
From: Nicholas N. <nj...@cs...> - 2008-05-28 07:56:50
|
On Wed, 28 May 2008, Andrei Soare wrote: > I am a GSoC student doing performance work for GNOME and I make use of > Valgrind's massif a lot in my work. > > I want to ask you about the possibility of determining the lifetime of > allocations during a program's execution. What I want to do is determine > those allocations that have short lifetime and try to replace them with > something else, perhaps static buffers, the main goal being to reduce the > memory fragmentation in GNOME. > >> From what I noticed, Massif doesn't say anything about deallocations (free / > delete), maybe I'm wrong ? > > Please let me know what I could do. Massif tracks deallocations, but you're right that it doesn't really say anything about them, or about allocation lifetimes. You could definitely track object lifetimes with a Valgrind tool, and Massif might be a good place to start because it has a lot of allocation-tracking infrastructure, but I expect you'd need to make substantial modifications to it. Nick |
|
From: <sv...@va...> - 2008-05-28 07:10:01
|
Author: bart
Date: 2008-05-28 08:09:54 +0100 (Wed, 28 May 2008)
New Revision: 8136
Log:
Removed the superfluous casts that were introduced in r8132.
Modified:
trunk/coregrind/m_syswrap/syswrap-linux.c
Modified: trunk/coregrind/m_syswrap/syswrap-linux.c
===================================================================
--- trunk/coregrind/m_syswrap/syswrap-linux.c 2008-05-27 16:08:24 UTC (rev 8135)
+++ trunk/coregrind/m_syswrap/syswrap-linux.c 2008-05-28 07:09:54 UTC (rev 8136)
@@ -1741,7 +1741,7 @@
if (linux_kernel_2_6_22())
{
/* 2.6.22 kernel: timerfd system call. */
- PRINT("sys_timerfd ( %d, %d, %p )", (int)ARG1, ARG2, ARG3);
+ PRINT("sys_timerfd ( %d, %d, %p )", ARG1, ARG2, ARG3);
PRE_REG_READ3(long, "sys_timerfd",
int, fd, int, clockid, const struct itimerspec *, tmr);
PRE_MEM_READ("timerfd(tmr)", ARG3,
@@ -2377,7 +2377,7 @@
PRE(sys_signalfd)
{
- PRINT("sys_signalfd ( %d, %p, %llu )", (int)ARG1, ARG2, (ULong) ARG3);
+ PRINT("sys_signalfd ( %d, %p, %llu )", ARG1, ARG2, (ULong) ARG3);
PRE_REG_READ3(long, "sys_signalfd",
int, fd, vki_sigset_t *, sigmask, vki_size_t, sigsetsize);
PRE_MEM_READ( "signalfd(sigmask)", ARG2, sizeof(vki_sigset_t) );
|
|
From: Andrei S. <and...@gm...> - 2008-05-28 06:29:45
|
Hello, I am a GSoC student doing performance work for GNOME and I make use of Valgrind's massif a lot in my work. I want to ask you about the possibility of determining the lifetime of allocations during a program's execution. What I want to do is determine those allocations that have short lifetime and try to replace them with something else, perhaps static buffers, the main goal being to reduce the memory fragmentation in GNOME. >From what I noticed, Massif doesn't say anything about deallocations (free / delete), maybe I'm wrong ? Please let me know what I could do. Thank you for your time. -- Andrei Soare |
|
From: Bart V. A. <bar...@gm...> - 2008-05-28 06:10:23
|
On Wed, May 28, 2008 at 1:22 AM, Julian Seward <js...@ac...> wrote: > lwarx and stwcx. are used together to create such sequences, but > there is no real constraint on what insns go between them, either > statically or dynamically. So there is no easy way, at JIT time, > to guarantee to observe that a given sequence represents an > atomic test-and-set (or whatever). At a guess I'd say it's > undecideable in general. That said, it is probably possible to > do better than at present by using some kind of idiom recognition > scheme, or IR analysis. But neither of those will be simple or > completely robust. I am familiar with how lwarx and stwcx work. But as far as I understand the VEX source code currently no information is passed by VEX to Valgrind tools about the bus snoop mechanism used by lwarx and stwcx. Do you think it would be a good idea to modify VEX such that it passes the following information to tools: * For lwarx instructions, the address being watched on the bus. * For stwcx instructions, the address for which the bus has been watched and whether or not another CPU has accessed that address since the bus watch started. Bart. |
|
From: Tom H. <th...@cy...> - 2008-05-28 02:57:26
|
Nightly build on aston ( x86_64, Fedora Core 5 ) started at 2008-05-28 03:20:05 BST 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 == 437 tests, 6 stderr failures, 1 stdout failure, 0 post failures == memcheck/tests/malloc_free_fill (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) none/tests/blockfault (stderr) none/tests/mremap2 (stdout) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc22_exit_w_lock (stderr) |
|
From: Tom H. <th...@cy...> - 2008-05-28 02:42:04
|
Nightly build on trojan ( x86_64, Fedora Core 6 ) started at 2008-05-28 03:25:07 BST 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 == 435 tests, 6 stderr failures, 5 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) memcheck/tests/x86/bug133694 (stdout) memcheck/tests/x86/bug133694 (stderr) memcheck/tests/x86/scalar (stderr) none/tests/cmdline1 (stdout) none/tests/cmdline2 (stdout) none/tests/mremap2 (stdout) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) ================================================= == 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 == 435 tests, 7 stderr failures, 5 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) memcheck/tests/x86/bug133694 (stdout) memcheck/tests/x86/bug133694 (stderr) memcheck/tests/x86/scalar (stderr) none/tests/cmdline1 (stdout) none/tests/cmdline2 (stdout) none/tests/mremap2 (stdout) helgrind/tests/tc17_sembar (stderr) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Wed May 28 03:33:47 2008 --- new.short Wed May 28 03:42:10 2008 *************** *** 8,10 **** ! == 435 tests, 7 stderr failures, 5 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) --- 8,10 ---- ! == 435 tests, 6 stderr failures, 5 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) *************** *** 17,19 **** none/tests/mremap2 (stdout) - helgrind/tests/tc17_sembar (stderr) helgrind/tests/tc20_verifywrap (stderr) --- 17,18 ---- |
|
From: Tom H. <th...@cy...> - 2008-05-28 02:37:23
|
Nightly build on dellow ( x86_64, Fedora 8 ) started at 2008-05-28 03:10:10 BST 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 == 431 tests, 7 stderr failures, 2 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) memcheck/tests/x86/scalar (stderr) none/tests/blockfault (stderr) none/tests/mremap2 (stdout) helgrind/tests/tc18_semabuse (stderr) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) |
|
From: Tom H. <th...@cy...> - 2008-05-28 02:35:27
|
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2008-05-28 03:05:06 BST 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 == 431 tests, 4 stderr failures, 2 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) memcheck/tests/x86/scalar (stderr) none/tests/mremap2 (stdout) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc22_exit_w_lock (stderr) |
|
From: Tom H. <th...@cy...> - 2008-05-28 02:27:13
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2008-05-28 03:15:02 BST Results unchanged 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 -c -o tls2_so.o `test -f 'tls2_so.c' || echo './'`tls2_so.c; \ then mv -f ".deps/tls2_so.Tpo" ".deps/tls2_so.Po"; \ else rm -f ".deps/tls2_so.Tpo"; exit 1; \ fi gcc -Winline -Wall -Wshadow -g -m32 -Wno-long-long -o tls2.so -shared tls2_so.o -lrt gcc -Winline -Wall -Wshadow -g -m32 -Wno-long-long -o tls.so -Wl,-rpath,../../none/tests -shared -fPIC tls_so-tls_so.o tls2.so -lrt gcc -Winline -Wall -Wshadow -g -m32 -Wno-long-long -o tls -Wl,-rpath,../../none/tests tls.o tls2.o tls.so -lpthread -lrt tls.so: undefined reference to `___tls_get_addr' collect2: ld returned 1 exit status make[5]: *** [tls] Error 1 make[5]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind/none/tests' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind/none/tests' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind' make: *** [check] Error 2 |
|
From: Tom H. <th...@cy...> - 2008-05-28 02:24:43
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2008-05-28 03:15:01 BST Results unchanged 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 -c -o tls2_so.o `test -f 'tls2_so.c' || echo './'`tls2_so.c; \ then mv -f ".deps/tls2_so.Tpo" ".deps/tls2_so.Po"; \ else rm -f ".deps/tls2_so.Tpo"; exit 1; \ fi gcc -Winline -Wall -Wshadow -g -m32 -Wno-long-long -o tls2.so -shared tls2_so.o -lrt gcc -Winline -Wall -Wshadow -g -m32 -Wno-long-long -o tls.so -Wl,-rpath,../../none/tests -shared -fPIC tls_so-tls_so.o tls2.so -lrt gcc -Winline -Wall -Wshadow -g -m32 -Wno-long-long -o tls -Wl,-rpath,../../none/tests tls.o tls2.o tls.so -lpthread -lrt tls.so: undefined reference to `___tls_get_addr' collect2: ld returned 1 exit status make[5]: *** [tls] Error 1 make[5]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind/none/tests' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind/none/tests' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/vgtest/2008-05-28/valgrind' make: *** [check] Error 2 |
|
From: Tom H. <th...@cy...> - 2008-05-28 02:23:17
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2008-05-28 03:00:02 BST 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 == 437 tests, 90 stderr failures, 3 stdout failures, 0 post failures == memcheck/tests/malloc_free_fill (stderr) memcheck/tests/origin5-bz2 (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/varinfo6 (stderr) memcheck/tests/x86/bug133694 (stderr) memcheck/tests/x86/bug152022 (stderr) memcheck/tests/x86/espindola2 (stderr) memcheck/tests/x86/fpeflags (stderr) memcheck/tests/x86/fprem (stderr) memcheck/tests/x86/fxsave (stderr) memcheck/tests/x86/insn_basic (stderr) memcheck/tests/x86/insn_cmov (stderr) memcheck/tests/x86/insn_fpu (stderr) memcheck/tests/x86/insn_mmx (stderr) memcheck/tests/x86/insn_mmxext (stderr) memcheck/tests/x86/insn_sse (stderr) memcheck/tests/x86/insn_sse2 (stderr) memcheck/tests/x86/int3-x86 (stderr) memcheck/tests/x86/more_x86_fp (stderr) memcheck/tests/x86/pushfpopf (stderr) memcheck/tests/x86/pushfw_x86 (stderr) memcheck/tests/x86/pushpopmem (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_exit_group (stderr) memcheck/tests/x86/scalar_fork (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/x86/scalar_vfork (stderr) memcheck/tests/x86/sse1_memory (stderr) memcheck/tests/x86/sse2_memory (stderr) memcheck/tests/x86/tronical (stderr) memcheck/tests/x86/xor-undef-x86 (stderr) cachegrind/tests/x86/fpu-28-108 (stderr) none/tests/amd64/insn_ssse3 (stdout) none/tests/amd64/insn_ssse3 (stderr) none/tests/amd64/ssse3_misaligned (stderr) none/tests/blockfault (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap2 (stdout) none/tests/x86/badseg (stderr) none/tests/x86/bt_everything (stderr) none/tests/x86/bt_literal (stderr) none/tests/x86/bug125959-x86 (stderr) none/tests/x86/bug126147-x86 (stderr) none/tests/x86/bug132813-x86 (stderr) none/tests/x86/bug135421-x86 (stderr) none/tests/x86/bug137714-x86 (stderr) none/tests/x86/bug152818-x86 (stderr) none/tests/x86/cmpxchg8b (stderr) none/tests/x86/cpuid (stderr) none/tests/x86/cse_fail (stderr) none/tests/x86/fcmovnu (stderr) none/tests/x86/fpu_lazy_eflags (stderr) none/tests/x86/fxtract (stderr) none/tests/x86/getseg (stderr) none/tests/x86/incdec_alt (stderr) none/tests/x86/insn_basic (stderr) none/tests/x86/insn_cmov (stderr) none/tests/x86/insn_fpu (stderr) none/tests/x86/insn_mmx (stderr) none/tests/x86/insn_mmxext (stderr) none/tests/x86/insn_sse (stderr) none/tests/x86/insn_sse2 (stderr) none/tests/x86/insn_sse3 (stderr) none/tests/x86/insn_ssse3 (stdout) none/tests/x86/insn_ssse3 (stderr) none/tests/x86/jcxz (stderr) none/tests/x86/lahf (stderr) none/tests/x86/looper (stderr) none/tests/x86/movx (stderr) none/tests/x86/pushpopseg (stderr) none/tests/x86/sbbmisc (stderr) none/tests/x86/seg_override (stderr) none/tests/x86/sigcontext (stderr) none/tests/x86/smc1 (stderr) none/tests/x86/ssse3_misaligned (stderr) helgrind/tests/hg01_all_ok (stderr) helgrind/tests/hg02_deadlock (stderr) helgrind/tests/hg03_inherit (stderr) helgrind/tests/hg04_race (stderr) helgrind/tests/hg05_race2 (stderr) helgrind/tests/tc01_simple_race (stderr) helgrind/tests/tc05_simple_race (stderr) helgrind/tests/tc06_two_races (stderr) helgrind/tests/tc09_bad_unlock (stderr) helgrind/tests/tc14_laog_dinphils (stderr) helgrind/tests/tc16_byterace (stderr) helgrind/tests/tc17_sembar (stderr) helgrind/tests/tc19_shadowmem (stderr) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) helgrind/tests/tc23_bogus_condwait (stderr) |
|
From: Julian S. <js...@ac...> - 2008-05-27 23:28:17
|
> If I remember correctly you added some time ago Imbe_BusLock / > Imbe_BusUnlock to VEX. Were these intended to be instruction-set > independent, or only to handle x86 bus locking ? In the last case, how > should tools like Helgrind or exp-drd handle atomic ppc instructions ? > See also http://bugs.kde.org/show_bug.cgi?id=162354. Well, the difficulty is that the powerpc way of doing atomic test-and-set (etc) is completely different from the x86/amd64 way. x86 and amd64 make it easy, by allowing a 1-byte LOCK prefix byte (0xF0) in front of the instruction. Vex sees that and puts Imbe_BusLock and Imbe_BusUnlock around the translation of the instruction, so helgrind and drd (and anybody else who cares) can see the locking. ppc has no direct equivalent. There is nothing to indicate that any single instruction is atomic. In any case, since ppc only allows simple load and store instructions, and not load-op-store insns, it would be useless to say that a single load or store is atomic (so what?) Instead ppc supplies what amounts to a programmable bus snoop mechanism, the lwarx and stwcx. instructions. These can be used to create atomic test-and-set sequences, etc, all the primitives you need. Google for these; there are many examples on the net. lwarx and stwcx. are used together to create such sequences, but there is no real constraint on what insns go between them, either statically or dynamically. So there is no easy way, at JIT time, to guarantee to observe that a given sequence represents an atomic test-and-set (or whatever). At a guess I'd say it's undecideable in general. That said, it is probably possible to do better than at present by using some kind of idiom recognition scheme, or IR analysis. But neither of those will be simple or completely robust. J |
|
From: Nicholas N. <nj...@cs...> - 2008-05-27 22:28:20
|
On Tue, 27 May 2008, John Reiser wrote:
>>> On x86, what is the status of getting FPU and SSE register state
>>> saved into (and restored from) the signal context, so that a signal handler
>>> can inspect and modify the values of FPU and SSE registers?
>>
>> It looks like the comment you quoted pretty much answers your
>> question doesn't it?
>
> No, the comment does not necessarily answer, "What is the status?"
> According to "svn blame sigframe-x86-linux.c", those lines are from
> r3265, and according to "svn log sigframe-x86-linux.c", r3265 was
> added on 2005-03-10, which is more than three years ago.
>
> Comments are not analyzed by the compiler.
> Comments are not checked by the regression tests.
> Comments are not exercised by running user code through the tools.
> Thus the natural tendency is for comments to become stale,
> particularly comments that employ future tense ("will be fixed.")
> Also, in a project such as valgrind the state of svn does not
> necessarily provide a good window into the state of activity.
>
> I was fishing for news about anyone else working in this area.
> By the [lack of] responses, so far I see that nobody else is.
John, your emails on this list are typically well-informed, but they are
often also terse, cryptic and/or aggressive. If you write that way, you
shouldn't be surprised if people respond in kind.
With respect to the particular FPU/SSE state problem: if you explain why
you need this shortcoming fixed -- eg. what program(s) it will enable --
that might help motivate someone to fix it. Your uses of Valgrind tend to
be more specialised and demanding than most people's, and obscure bugs tend
to be lower priority.
Nick
|
|
From: John R.
|
Tom Hughes wrote:
> In message <483B2615.2050600@BitWagon.com>
> John Reiser <jreiser@BitWagon.com> wrote:
>
>
>>On x86, what is the status of getting FPU and SSE register state
>>saved into (and restored from) the signal context, so that a signal handler
>>can inspect and modify the values of FPU and SSE registers?
>
>
> It looks like the comment you quoted pretty much answers your
> question doesn't it?
No, the comment does not necessarily answer, "What is the status?"
According to "svn blame sigframe-x86-linux.c", those lines are from
r3265, and according to "svn log sigframe-x86-linux.c", r3265 was
added on 2005-03-10, which is more than three years ago.
Comments are not analyzed by the compiler.
Comments are not checked by the regression tests.
Comments are not exercised by running user code through the tools.
Thus the natural tendency is for comments to become stale,
particularly comments that employ future tense ("will be fixed.")
Also, in a project such as valgrind the state of svn does not
necessarily provide a good window into the state of activity.
I was fishing for news about anyone else working in this area.
By the [lack of] responses, so far I see that nobody else is.
--
|
|
From: <sv...@va...> - 2008-05-27 16:09:06
|
Author: sewardj
Date: 2008-05-27 17:08:24 +0100 (Tue, 27 May 2008)
New Revision: 8135
Log:
Add a missing case and remove the bogus associated comment.
Modified:
trunk/memcheck/mc_machine.c
Modified: trunk/memcheck/mc_machine.c
===================================================================
--- trunk/memcheck/mc_machine.c 2008-05-27 13:40:36 UTC (rev 8134)
+++ trunk/memcheck/mc_machine.c 2008-05-27 16:08:24 UTC (rev 8135)
@@ -511,11 +511,7 @@
if (o == GOF(FTOP) && szB == 4) return -1;
if (o == GOF(FPROUND) && szB == 8) return -1;
if (o == GOF(EMWARN) && szB == 4) return -1;
- /* The amd64 front end doesn't actually use FC3210. It should
- be done away with.
- if (offset == offsetof(VexGuestAMD64State,guest_FC3210) && szB==4)
- return -1;
- */
+ if (o == GOF(FC3210) && szB == 8) return -1;
/* XMM registers */
if (o >= GOF(XMM0) && o+sz <= GOF(XMM0) +SZB(XMM0)) return GOF(XMM0);
|
|
From: <sv...@va...> - 2008-05-27 13:40:35
|
Author: bart
Date: 2008-05-27 14:40:36 +0100 (Tue, 27 May 2008)
New Revision: 8134
Log:
Make the rlimit_nofile regression tests less system dependent.
Modified:
trunk/none/tests/rlimit_nofile.c
Modified: trunk/none/tests/rlimit_nofile.c
===================================================================
--- trunk/none/tests/rlimit_nofile.c 2008-05-27 12:33:29 UTC (rev 8133)
+++ trunk/none/tests/rlimit_nofile.c 2008-05-27 13:40:36 UTC (rev 8134)
@@ -4,13 +4,16 @@
#include <stdlib.h>
#include <sys/resource.h>
#include <unistd.h>
+#include "fdleak.h"
int main(int argc, char **argv)
{
struct rlimit oldrlim;
struct rlimit newrlim;
int fd;
- close(4); /* seems to be inherited from parent on SuSE 10.1 amd64 */
+
+ CLOSE_INHERITED_FDS;
+
if (getrlimit(RLIMIT_NOFILE, &oldrlim) < 0)
{
perror("getrlimit");
|
|
From: <sv...@va...> - 2008-05-27 12:33:26
|
Author: bart Date: 2008-05-27 13:33:29 +0100 (Tue, 27 May 2008) New Revision: 8133 Log: Make the fdleak regression tests less system dependent. Added: trunk/none/tests/fdleak.h Modified: trunk/none/tests/fdleak_cmsg.c trunk/none/tests/fdleak_creat.c trunk/none/tests/fdleak_dup.c trunk/none/tests/fdleak_dup2.c trunk/none/tests/fdleak_fcntl.c trunk/none/tests/fdleak_ipv4.c trunk/none/tests/fdleak_open.c trunk/none/tests/fdleak_pipe.c trunk/none/tests/fdleak_socketpair.c Added: trunk/none/tests/fdleak.h =================================================================== --- trunk/none/tests/fdleak.h (rev 0) +++ trunk/none/tests/fdleak.h 2008-05-27 12:33:29 UTC (rev 8133) @@ -0,0 +1,15 @@ +#ifndef _FDLEAK_H_ +#define _FDLEAK_H_ + +/* + * The macro below closes file descriptors inherited from the process + * that forked the current process. Close these file descriptors right + * after the start of main() in order to get consistent results across + * different releases. Known behavior: + * - Fedora Core 1's Perl opens /dev/pts/2 as fd 10. + * - For Ubuntu 8.04, see also + * https://bugs.launchpad.net/ubuntu/+source/seahorse/+bug/235184 + */ +#define CLOSE_INHERITED_FDS { int i; for (i = 3; i < 64; i++) close(i); } + +#endif /* _FDLEAK_H_ */ Modified: trunk/none/tests/fdleak_cmsg.c =================================================================== --- trunk/none/tests/fdleak_cmsg.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_cmsg.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -27,8 +27,8 @@ #include <unistd.h> #include <stdlib.h> #include <errno.h> +#include "fdleak.h" - char filea[24]; char fileb[24]; char sock[24]; @@ -179,13 +179,13 @@ { int pid, status; - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); close(4); + + + + CLOSE_INHERITED_FDS; + pid = getpid(); sprintf(filea, "/tmp/data1.%d", pid); sprintf(fileb, "/tmp/data2.%d", pid); Modified: trunk/none/tests/fdleak_creat.c =================================================================== --- trunk/none/tests/fdleak_creat.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_creat.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -1,19 +1,19 @@ #include <unistd.h> #include <stdio.h> #include <fcntl.h> - +#include "fdleak.h" int main (int argc, char **argv) { char filename[24]; - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); close(4); + + + + CLOSE_INHERITED_FDS; + sprintf(filename, "/tmp/file.%d\n", getpid()); creat(filename, 0); unlink(filename); Modified: trunk/none/tests/fdleak_dup.c =================================================================== --- trunk/none/tests/fdleak_dup.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_dup.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -1,18 +1,18 @@ #include <unistd.h> #include <fcntl.h> - +#include "fdleak.h" int main (int argc, char **argv) { int s; - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); close(4); + + + + CLOSE_INHERITED_FDS; + s = open("/dev/null", O_RDONLY); dup(s); return 0; Modified: trunk/none/tests/fdleak_dup2.c =================================================================== --- trunk/none/tests/fdleak_dup2.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_dup2.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -1,19 +1,19 @@ #include <unistd.h> #include <fcntl.h> - +#include "fdleak.h" int main (int argc, char **argv) { int s1; int s2; - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); close(4); + + + + CLOSE_INHERITED_FDS; + s1 = open("/dev/null", O_RDONLY); s2 = open("/dev/null", O_RDONLY); Modified: trunk/none/tests/fdleak_fcntl.c =================================================================== --- trunk/none/tests/fdleak_fcntl.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_fcntl.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -1,19 +1,19 @@ #include <unistd.h> #include <stdio.h> #include <fcntl.h> - +#include "fdleak.h" int main (int argc, char **argv) { int s1; - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); close(4); + + + + CLOSE_INHERITED_FDS; + s1 = open("/dev/null", O_RDONLY); if(fcntl(s1, F_DUPFD, s1) == -1) perror("fcntl"); return 0; Modified: trunk/none/tests/fdleak_ipv4.c =================================================================== --- trunk/none/tests/fdleak_ipv4.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_ipv4.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -8,7 +8,7 @@ #include <unistd.h> #include <stdlib.h> #include <string.h> - +#include "fdleak.h" void server () { @@ -89,13 +89,13 @@ { int pid, status; - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); close(4); + + + + CLOSE_INHERITED_FDS; + if((pid = fork()) == 0) { server(); return 0; Modified: trunk/none/tests/fdleak_open.c =================================================================== --- trunk/none/tests/fdleak_open.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_open.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -1,15 +1,15 @@ #include <fcntl.h> #include <unistd.h> +#include "fdleak.h" + int main (int argc, char **argv) { - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); close(4); + + CLOSE_INHERITED_FDS; + open("/dev/null", O_RDONLY); return 0; } Modified: trunk/none/tests/fdleak_pipe.c =================================================================== --- trunk/none/tests/fdleak_pipe.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_pipe.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -1,17 +1,17 @@ #include <unistd.h> - +#include "fdleak.h" int main (int argc, char **argv) { int fds[2]; - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); + + + + CLOSE_INHERITED_FDS; + pipe(fds); return 0; } Modified: trunk/none/tests/fdleak_socketpair.c =================================================================== --- trunk/none/tests/fdleak_socketpair.c 2008-05-26 17:16:08 UTC (rev 8132) +++ trunk/none/tests/fdleak_socketpair.c 2008-05-27 12:33:29 UTC (rev 8133) @@ -1,17 +1,17 @@ #include <sys/socket.h> #include <unistd.h> +#include "fdleak.h" + int main (int argc, char **argv) { int fds[2]; - /* - * Fedora Core 1's Perl opens /dev/pts/2 as fd 10. Let's close it - * now to get consistent results across different releases. - */ - close(10); close(4); + + CLOSE_INHERITED_FDS; + socketpair(AF_UNIX, SOCK_STREAM, PF_UNIX, fds); return 0; } |
|
From: Bart V. A. <bar...@gm...> - 2008-05-27 06:04:07
|
On Mon, May 26, 2008 at 4:23 AM, Tom Hughes <th...@cy...> wrote: > > Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2008-05-26 03:00:02 BST > Results differ from 24 hours ago Hello Tom, Do you see any clue in the *diff* files about why the number of failed regression tests increased from 30 to 90 on Fedora Core 2 ? Bart. |
|
From: Tom H. <th...@cy...> - 2008-05-27 02:57:05
|
Nightly build on aston ( x86_64, Fedora Core 5 ) started at 2008-05-27 03:20:07 BST 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 == 437 tests, 7 stderr failures, 1 stdout failure, 0 post failures == memcheck/tests/malloc_free_fill (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) none/tests/blockfault (stderr) none/tests/mremap2 (stdout) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) |
|
From: Tom H. <th...@cy...> - 2008-05-27 02:41:46
|
Nightly build on trojan ( x86_64, Fedora Core 6 ) started at 2008-05-27 03:25:04 BST 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 == 435 tests, 7 stderr failures, 5 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) memcheck/tests/x86/bug133694 (stdout) memcheck/tests/x86/bug133694 (stderr) memcheck/tests/x86/scalar (stderr) none/tests/cmdline1 (stdout) none/tests/cmdline2 (stdout) none/tests/mremap2 (stdout) helgrind/tests/tc17_sembar (stderr) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) ================================================= == 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 == 435 tests, 6 stderr failures, 5 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) memcheck/tests/x86/bug133694 (stdout) memcheck/tests/x86/bug133694 (stderr) memcheck/tests/x86/scalar (stderr) none/tests/cmdline1 (stdout) none/tests/cmdline2 (stdout) none/tests/mremap2 (stdout) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc21_pthonce (stderr) helgrind/tests/tc22_exit_w_lock (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue May 27 03:33:32 2008 --- new.short Tue May 27 03:41:52 2008 *************** *** 8,10 **** ! == 435 tests, 6 stderr failures, 5 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) --- 8,10 ---- ! == 435 tests, 7 stderr failures, 5 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) *************** *** 17,18 **** --- 17,19 ---- none/tests/mremap2 (stdout) + helgrind/tests/tc17_sembar (stderr) helgrind/tests/tc20_verifywrap (stderr) |
|
From: Tom H. <th...@cy...> - 2008-05-27 02:40:49
|
Nightly build on lloyd ( x86_64, Fedora 7 ) started at 2008-05-27 03:05:04 BST 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 == 431 tests, 4 stderr failures, 2 stdout failures, 0 post failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) memcheck/tests/x86/scalar (stderr) none/tests/mremap2 (stdout) helgrind/tests/tc20_verifywrap (stderr) helgrind/tests/tc22_exit_w_lock (stderr) |