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
(12) |
|
2
(6) |
3
(13) |
4
(9) |
5
(6) |
6
(8) |
7
(5) |
8
(5) |
|
9
(15) |
10
(18) |
11
(18) |
12
(18) |
13
(7) |
14
(11) |
15
(6) |
|
16
(12) |
17
(28) |
18
(15) |
19
(12) |
20
(17) |
21
(23) |
22
(10) |
|
23
(9) |
24
(11) |
25
(7) |
26
(21) |
27
(12) |
28
(6) |
29
(6) |
|
30
(8) |
|
|
|
|
|
|
|
From: Nicholas N. <nj...@cs...> - 2007-09-11 22:39:19
|
On Tue, 11 Sep 2007, Eric Hopper wrote: > I know very little about NetBSD vs. FreeBSD. Isn't it true that NetBSD > uses a.out whereas FreeBSD uses ELF? Will this matter much as far as > Valgrind is concerned? I know it will matter at least a little since > Valgrind relies a bit on shared library hooks, but the description I see > in the technical documentation section doesn't imply a major reliance on > a particular object file format. It will matter a lot -- Valgrind has its own ELF loader. Although, does AIX use ELF or a.out? If the latter, then Valgrind must have its own a.out loader too, I think... Nick |
|
From: Eric H. <eri...@is...> - 2007-09-11 18:41:25
|
On Tue, 2007-09-11 at 15:31 +0200, Peter Bex wrote: > On Mon, Sep 10, 2007 at 06:07:46PM -0700, Eric Hopper wrote: > > What would be involved in porting the latest version? It seems like > > FreeBSD has a version in the ports tree, but that version is really old. > > > > Also, the Valgrind Technical Documentation appears really out-of-date. > > In particular it doesn't seem to mention threads at all. > > There's work in progress on the NetBSD port. Have a look at > http://vg4nbsd.sourceforge.net for more information. Actually... http://vg4nbsd.berlios.de/ is the right URL. :-) > If you have some time and energy to spend, we'd very much appreciate > some help. The port currently works on simple programs. We need > support for signal handling. Basically we are now ensuring that the > tests run. It would be reasonably simple to port it to FreeBSD. > There is also work being done by Apple on a port for Darwin, which > would be similar, but this work will only be open sourced when it is > finished. I know very little about NetBSD vs. FreeBSD. Isn't it true that NetBSD uses a.out whereas FreeBSD uses ELF? Will this matter much as far as Valgrind is concerned? I know it will matter at least a little since Valgrind relies a bit on shared library hooks, but the description I see in the technical documentation section doesn't imply a major reliance on a particular object file format. But I can see a difference in object file format possibly posing a barrier to a NetBSD vs. a FreeBSD port. I'm concerned mainly with FreeBSD because the company I'm working for will need to modify it even further because the devices we sell use a somewhat modified FreeBSD kernel. I would love to be able to help, but in order to be paid to do so I need to be able to justify it to the people I'm working for. :-) Thanks, -- Eric Hopper <eri...@is...> Isilon Systems |
|
From: Benjamin M. <be...@me...> - 2007-09-11 18:06:10
|
Nice :) Hmm it probably wouldn't take much work (cross fingers) to get KCachegrind built on Qt4 only. Slap in a few OS X integration features and have a nice bundle to run on my laptop :) -Benjamin Meyer On Sep 11, 2007, at 7:18 PM, Peter Bex wrote: > On Tue, Sep 11, 2007 at 07:09:09PM +0200, Benjamin Meyer wrote: >> >> On Sep 11, 2007, at 3:31 PM, Peter Bex wrote: >> >>> There is also work >>> being done by Apple on a port for Darwin, which would be similar, >>> but this work will only be open sourced when it is finished. >> >> Do you have any more information about this? Is this something that >> someone at apple talked about doing or is actually doing? Any time >> table? >> >> -Benjamin Meyer > > See > http://sourceforge.net/mailarchive/forum.php? > thread_name=20070831232811.7178.qmail% > 40kaazh.pair.com&forum_name=valgrind-developers > > Peter > -- > http://sjamaan.ath.cx > -- > "The process of preparing programs for a digital computer > is especially attractive, not only because it can be economically > and scientifically rewarding, but also because it can be an aesthetic > experience much like composing poetry or music." > -- Donald Knuth > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2005. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers |
|
From: Peter B. <Pet...@xs...> - 2007-09-11 17:19:25
|
On Tue, Sep 11, 2007 at 07:09:09PM +0200, Benjamin Meyer wrote: >=20 > On Sep 11, 2007, at 3:31 PM, Peter Bex wrote: >=20 > > There is also work > > being done by Apple on a port for Darwin, which would be similar, > > but this work will only be open sourced when it is finished. >=20 > Do you have any more information about this? Is this something that =20 > someone at apple talked about doing or is actually doing? Any time =20 > table? >=20 > -Benjamin Meyer See http://sourceforge.net/mailarchive/forum.php?thread_name=3D20070831232811.7= 178.qmail%40kaazh.pair.com&forum_name=3Dvalgrind-developers Peter --=20 http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth |
|
From: Benjamin M. <be...@me...> - 2007-09-11 17:10:21
|
On Sep 11, 2007, at 3:31 PM, Peter Bex wrote: > There is also work > being done by Apple on a port for Darwin, which would be similar, > but this work will only be open sourced when it is finished. Do you have any more information about this? Is this something that someone at apple talked about doing or is actually doing? Any time table? -Benjamin Meyer |
|
From: <sv...@va...> - 2007-09-11 15:07:18
|
Author: sewardj Date: 2007-09-11 16:07:20 +0100 (Tue, 11 Sep 2007) New Revision: 6821 Log: Add docs (start with Helgrind's for now) Added: branches/THRCHECK/thrcheck/docs/tc-manual.xml Added: branches/THRCHECK/thrcheck/docs/tc-manual.xml =================================================================== --- branches/THRCHECK/thrcheck/docs/tc-manual.xml (rev 0) +++ branches/THRCHECK/thrcheck/docs/tc-manual.xml 2007-09-11 15:07:20 UTC (rev 6821) @@ -0,0 +1,106 @@ +<?xml version="1.0"?> <!-- -*- sgml -*- --> +<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" + "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"> + + +<chapter id="hg-manual" xreflabel="Helgrind: a data-race detector"> + <title>Helgrind: a data-race detector</title> + +<para>To use this tool, you must specify +<computeroutput>--tool=helgrind</computeroutput> on the Valgrind +command line.</para> + +<para>Note: Helgrind does not work in Valgrind 3.1.0. We hope +to reinstate in version 3.2.0.</para> + + +<sect1 id="hg-manual.data-races" xreflabel="Data Races"> +<title>Data Races</title> + +<para>Helgrind is a valgrind tool for detecting data races in C and C++ +programs that use the Pthreads library.</para> + +<para>It uses the Eraser algorithm described in: + + <address>Eraser: A Dynamic Data Race Detector for Multithreaded Programs + Stefan Savage, Michael Burrows, Greg Nelson, Patrick Sobalvarro and Thomas Anderson + ACM Transactions on Computer Systems, 15(4):391-411 + November 1997. + </address> +</para> + +<para>We also incorporate significant improvements from this paper: + + <address>Runtime Checking of Multithreaded Applications with Visual Threads + Jerry J. Harrow, Jr. + Proceedings of the 7th International SPIN Workshop on Model Checking of Software + Stanford, California, USA + August 2000 + LNCS 1885, pp331--342 + K. Havelund, J. Penix, and W. Visser, editors. + </address> +</para> + +</sect1> + + +<sect1 id="hg-manual.what-does" xreflabel="What Helgrind Does"> +<title>What Helgrind Does</title> + +<para>Basically what Helgrind does is to look for memory +locations which are accessed by more than one thread. For each +such location, Helgrind records which of the program's +(pthread_mutex_)locks were held by the accessing thread at the +time of the access. The hope is to discover that there is indeed +at least one lock which is used by all threads to protect that +location. If no such lock can be found, then there is +(apparently) no consistent locking strategy being applied for +that location, and so a possible data race might result.</para> + +<para>Helgrind also allows for "thread segment lifetimes". If +the execution of two threads cannot overlap -- for example, if +your main thread waits on another thread with a +<computeroutput>pthread_join()</computeroutput> operation -- they +can both access the same variable without holding a lock.</para> + +<para>There's a lot of other sophistication in Helgrind, aimed at +reducing the number of false reports, and at producing useful +error reports. We hope to have more documentation one +day ... </para> + +</sect1> + + + +<sect1 id="hg-manual.options" xreflabel="Helgrind Options"> +<title>Helgrind Options</title> + +<para>Helgrind-specific options are:</para> + +<!-- start of xi:include in the manpage --> +<variablelist id="hg.opts.list"> + + <varlistentry id="opt.private-stacks" xreflabel="--private-stacks"> + <term> + <option><![CDATA[--private-stacks=<yes|no> [default: no] ]]></option> + </term> + <listitem> + <para>Assume thread stacks are used privately.</para> + </listitem> + </varlistentry> + + <varlistentry id="opt.show-last-access" xreflabel="--show-last-access"> + <term> + <option><![CDATA[--show-last-access=<yes|some|no> [default: no] ]]></option> + </term> + <listitem> + <para>Show location of last word access on error.</para> + </listitem> + </varlistentry> + +</variablelist> +<!-- end of xi:include in the manpage --> + +</sect1> + +</chapter> |
|
From: <sv...@va...> - 2007-09-11 15:06:34
|
Author: sewardj Date: 2007-09-11 16:06:34 +0100 (Tue, 11 Sep 2007) New Revision: 6820 Log: A 'make dist' fix (merge to trunk) Modified: branches/THRCHECK/none/tests/amd64/Makefile.am Modified: branches/THRCHECK/none/tests/amd64/Makefile.am =================================================================== --- branches/THRCHECK/none/tests/amd64/Makefile.am 2007-09-11 13:52:01 UTC (rev 6819) +++ branches/THRCHECK/none/tests/amd64/Makefile.am 2007-09-11 15:06:34 UTC (rev 6820) @@ -34,7 +34,7 @@ smc1.stderr.exp smc1.stdout.exp smc1.vgtest \ shrld.stderr.exp shrld.stdout.exp shrld.vgtest \ slahf-amd64.stderr.exp slahf-amd64.stdout.exp \ - slahf-amd64.stderr.vgtest + slahf-amd64.vgtest check_PROGRAMS = \ |
|
From: <sv...@va...> - 2007-09-11 13:52:02
|
Author: sewardj
Date: 2007-09-11 14:52:01 +0100 (Tue, 11 Sep 2007)
New Revision: 6819
Log:
Make thrcheck work on ppc32-linux.
Modified:
branches/THRCHECK/coregrind/m_syswrap/syswrap-ppc32-linux.c
branches/THRCHECK/thrcheck/tests/tc07_hbl1.c
branches/THRCHECK/thrcheck/tests/tc08_hbl2.c
Modified: branches/THRCHECK/coregrind/m_syswrap/syswrap-ppc32-linux.c
===================================================================
--- branches/THRCHECK/coregrind/m_syswrap/syswrap-ppc32-linux.c 2007-09-11 10:26:28 UTC (rev 6818)
+++ branches/THRCHECK/coregrind/m_syswrap/syswrap-ppc32-linux.c 2007-09-11 13:52:01 UTC (rev 6819)
@@ -313,6 +313,12 @@
ctst->client_stack_szB = 0;
}
+ /* Assume the clone will succeed, and tell any tool that wants to
+ know that this thread has come into existence. If the clone
+ fails, we'll send out a ll_exit notification for it at the out:
+ label below, to clean up. */
+ VG_TRACK ( pre_thread_ll_create, ptid, ctid );
+
if (flags & VKI_CLONE_SETTLS) {
if (debug)
VG_(printf)("clone child has SETTLS: tls at %p\n", child_tls);
@@ -344,6 +350,8 @@
/* clone failed */
VG_(cleanup_thread)(&ctst->arch);
ctst->status = VgTs_Empty;
+ /* oops. Better tell the tool the thread exited in a hurry :-) */
+ VG_TRACK( pre_thread_ll_exit, ctid );
}
return res;
Modified: branches/THRCHECK/thrcheck/tests/tc07_hbl1.c
===================================================================
--- branches/THRCHECK/thrcheck/tests/tc07_hbl1.c 2007-09-11 10:26:28 UTC (rev 6818)
+++ branches/THRCHECK/thrcheck/tests/tc07_hbl1.c 2007-09-11 13:52:01 UTC (rev 6819)
@@ -32,6 +32,17 @@
# define INC(_lval) \
__asm__ __volatile__ ( \
"lock ; incl (%0)" : /*out*/ : /*in*/"r"(&(_lval)) : "memory", "cc" )
+#elif defined(PLAT_ppc32_linux)
+# define INC(_lval) \
+ __asm__ __volatile__( \
+ "1:\n" \
+ " lwarx 15,0,%0\n" \
+ " addi 15,15,1\n" \
+ " stwcx. 15,0,%0\n" \
+ " bne- 1b" \
+ : /*out*/ : /*in*/ "b"(&(_lval)) \
+ : /*trash*/ "r15", "cr0", "memory" \
+ )
#else
# error "Fix Me for this platform"
#endif
Modified: branches/THRCHECK/thrcheck/tests/tc08_hbl2.c
===================================================================
--- branches/THRCHECK/thrcheck/tests/tc08_hbl2.c 2007-09-11 10:26:28 UTC (rev 6818)
+++ branches/THRCHECK/thrcheck/tests/tc08_hbl2.c 2007-09-11 13:52:01 UTC (rev 6819)
@@ -36,6 +36,17 @@
# define INC(_lval) \
__asm__ __volatile__ ( \
"lock ; incl (%0)" : /*out*/ : /*in*/"r"(&(_lval)) : "memory", "cc" )
+#elif defined(PLAT_ppc32_linux)
+# define INC(_lval) \
+ __asm__ __volatile__( \
+ "1:\n" \
+ " lwarx 15,0,%0\n" \
+ " addi 15,15,1\n" \
+ " stwcx. 15,0,%0\n" \
+ " bne- 1b" \
+ : /*out*/ : /*in*/ "b"(&(_lval)) \
+ : /*trash*/ "r15", "cr0", "memory" \
+ )
#else
# error "Fix Me for this platform"
#endif
|
|
From: Peter B. <Pet...@xs...> - 2007-09-11 13:31:44
|
On Mon, Sep 10, 2007 at 06:07:46PM -0700, Eric Hopper wrote: > What would be involved in porting the latest version? It seems like > FreeBSD has a version in the ports tree, but that version is really old. >=20 > Also, the Valgrind Technical Documentation appears really out-of-date. > In particular it doesn't seem to mention threads at all. There's work in progress on the NetBSD port. Have a look at http://vg4nbsd.sourceforge.net for more information. If you have some time and energy to spend, we'd very much appreciate some help. The port currently works on simple programs. We need support for signal handling. Basically we are now ensuring that the tests run. It would be reasonably simple to port it to FreeBSD. There is also work being done by Apple on a port for Darwin, which would be similar, but this work will only be open sourced when it is finished. Cheers, Peter --=20 http://sjamaan.ath.cx -- "The process of preparing programs for a digital computer is especially attractive, not only because it can be economically and scientifically rewarding, but also because it can be an aesthetic experience much like composing poetry or music." -- Donald Knuth |
|
From: <js...@ac...> - 2007-09-11 12:36:00
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2007-09-11 09:00:01 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 == 220 tests, 10 stderr failures, 8 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) none/tests/pth_detached (stdout) none/tests/tls (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, 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) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Tue Sep 11 09:12:57 2007 --- new.short Tue Sep 11 09:27:10 2007 *************** *** 8,10 **** ! == 220 tests, 10 stderr failures, 6 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) --- 8,10 ---- ! == 220 tests, 10 stderr failures, 8 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) *************** *** 25,26 **** --- 25,28 ---- none/tests/ppc32/test_gx (stdout) + none/tests/pth_detached (stdout) + none/tests/tls (stdout) |
|
From: <sv...@va...> - 2007-09-11 10:26:29
|
Author: sewardj
Date: 2007-09-11 11:26:28 +0100 (Tue, 11 Sep 2007)
New Revision: 6818
Log:
* x86-linux build fixes for regtests
* some suppressions for glibc-2.4 based systems
Modified:
branches/THRCHECK/glibc-2.4.supp
branches/THRCHECK/thrcheck/tests/tc07_hbl1.c
branches/THRCHECK/thrcheck/tests/tc08_hbl2.c
Modified: branches/THRCHECK/glibc-2.4.supp
===================================================================
--- branches/THRCHECK/glibc-2.4.supp 2007-09-10 21:35:49 UTC (rev 6817)
+++ branches/THRCHECK/glibc-2.4.supp 2007-09-11 10:26:28 UTC (rev 6818)
@@ -259,3 +259,40 @@
obj:/lib/libpthread-0.10.so
fun:pthread_create
}
+
+
+##----------------------------------------------------------------------##
+# Thrcheck tool, x86-linux, glibc-2.4
+{
+ thrcheck-glibc24-x86-1
+ Thrcheck:Race
+ fun:pthread_join*
+ fun:pthread_join*
+}
+{
+ thrcheck-glibc24-x86-2
+ Thrcheck:Race
+ fun:_dl_lookup_symbol_x
+ fun:_dl_fixup
+ fun:_dl_runtime_resolve
+}
+{
+ thrcheck-glibc24-x86-3
+ Thrcheck:Race
+ fun:__free_tcb
+ fun:pthread_join*
+ fun:pthread_join*
+}
+{
+ thrcheck-glibc24-x86-4
+ Thrcheck:Race
+ fun:pthread_mutex_lock*
+ fun:pthread_mutex_lock*
+}
+{
+ thrcheck-glibc24-x86-5
+ Thrcheck:Race
+ fun:do_clone
+ fun:pthread_create*
+ fun:pthread_create*
+}
Modified: branches/THRCHECK/thrcheck/tests/tc07_hbl1.c
===================================================================
--- branches/THRCHECK/thrcheck/tests/tc07_hbl1.c 2007-09-10 21:35:49 UTC (rev 6817)
+++ branches/THRCHECK/thrcheck/tests/tc07_hbl1.c 2007-09-11 10:26:28 UTC (rev 6818)
@@ -28,7 +28,7 @@
#endif
-#if defined(PLAT_amd64_linux)
+#if defined(PLAT_amd64_linux) || defined(PLAT_x86_linux)
# define INC(_lval) \
__asm__ __volatile__ ( \
"lock ; incl (%0)" : /*out*/ : /*in*/"r"(&(_lval)) : "memory", "cc" )
Modified: branches/THRCHECK/thrcheck/tests/tc08_hbl2.c
===================================================================
--- branches/THRCHECK/thrcheck/tests/tc08_hbl2.c 2007-09-10 21:35:49 UTC (rev 6817)
+++ branches/THRCHECK/thrcheck/tests/tc08_hbl2.c 2007-09-11 10:26:28 UTC (rev 6818)
@@ -32,7 +32,7 @@
#endif
-#if defined(PLAT_amd64_linux)
+#if defined(PLAT_amd64_linux) || defined(PLAT_x86_linux)
# define INC(_lval) \
__asm__ __volatile__ ( \
"lock ; incl (%0)" : /*out*/ : /*in*/"r"(&(_lval)) : "memory", "cc" )
|
|
From: Nicholas N. <nj...@cs...> - 2007-09-11 05:45:40
|
On Mon, 10 Sep 2007 sv...@va... wrote: > This is Thrcheck How do you pronounce that? Nick |
|
From: Tom H. <th...@cy...> - 2007-09-11 02:31:44
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-09-11 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 Regression test results follow == 256 tests, 27 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/addressable (stderr) memcheck/tests/badjump (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) 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-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/long_namespace_xml (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/x86/xor-undef-x86 (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2007-09-11 02:23:42
|
Nightly build on dellow ( x86_64, Fedora 7 ) started at 2007-09-11 03:10: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 == 293 tests, 4 stderr failures, 3 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/vcpu_fnfns (stdout) 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-09-11 02:19:28
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2007-09-11 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 == 293 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: Tom H. <th...@cy...> - 2007-09-11 02:16:49
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-09-11 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 == 295 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Eric H. <eri...@is...> - 2007-09-11 01:07:43
|
What would be involved in porting the latest version? It seems like FreeBSD has a version in the ports tree, but that version is really old. Also, the Valgrind Technical Documentation appears really out-of-date. In particular it doesn't seem to mention threads at all. Thanks, -- Eric Hopper <eri...@is...> Isilon Systems |
|
From: <js...@ac...> - 2007-09-11 00:17:16
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-09-11 02:00:01 CEST 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 == 228 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) |