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
(1) |
|
2
(28) |
3
(21) |
4
(27) |
5
(22) |
6
(24) |
7
(25) |
8
(21) |
|
9
(18) |
10
(20) |
11
(10) |
12
(36) |
13
(18) |
14
(18) |
15
(29) |
|
16
(17) |
17
(7) |
18
(11) |
19
(17) |
20
(18) |
21
(12) |
22
(13) |
|
23
(9) |
24
(8) |
25
(7) |
26
(22) |
27
(18) |
28
(9) |
29
(15) |
|
30
(13) |
31
(7) |
|
|
|
|
|
|
From: <sv...@va...> - 2005-10-16 17:48:11
|
Author: njn
Date: 2005-10-16 18:48:09 +0100 (Sun, 16 Oct 2005)
New Revision: 4939
Log:
augment comment
Modified:
trunk/include/pub_tool_tooliface.h
Modified: trunk/include/pub_tool_tooliface.h
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/include/pub_tool_tooliface.h 2005-10-16 13:52:50 UTC (rev 4938)
+++ trunk/include/pub_tool_tooliface.h 2005-10-16 17:48:09 UTC (rev 4939)
@@ -262,7 +262,9 @@
/* Does the tool need shadow memory allocated? */
extern void VG_(needs_shadow_memory)( void );
=20
-/* Does the tool replace malloc() and friends with its own versions? */
+/* Does the tool replace malloc() and friends with its own versions?
+ This has to be combined with the use of a vgpreload_<tool>.so module
+ or it won't work. See massif/Makefile.am for how to build it. */
// The 'p' prefix avoids GCC complaints about overshadowing global names=
.
extern void VG_(needs_malloc_replacement)(
void* (*pmalloc) ( ThreadId tid, SizeT n ),
|
|
From: <sv...@va...> - 2005-10-16 17:43:09
|
Author: njn Date: 2005-10-16 18:43:02 +0100 (Sun, 16 Oct 2005) New Revision: 224 Log: Fix another broken link. This is painful to watch, isn't it? Modified: trunk/docs/manual/manual-core.html Modified: trunk/docs/manual/manual-core.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/manual/manual-core.html 2005-10-16 17:20:32 UTC (rev 223) +++ trunk/docs/manual/manual-core.html 2005-10-16 17:43:02 UTC (rev 224) @@ -1303,7 +1303,7 @@ effect before dying in this way. This is a known problem which we should fix.</p> <p>Read the=20 -<a href=3D"http://www.valgrind.org/docs/faq/index.html" target=3D"_top">= FAQ</a> for +<a href=3D"http://www.valgrind.org/docs/FAQ/index.html" target=3D"_top">= FAQ</a> for more advice about common problems, crashes, etc.</p> </div> <div class=3D"sect1" lang=3D"en"> |
|
From: <sv...@va...> - 2005-10-16 17:20:38
|
Author: njn Date: 2005-10-16 18:20:32 +0100 (Sun, 16 Oct 2005) New Revision: 223 Log: try again Modified: trunk/docs/quick-start.html Modified: trunk/docs/quick-start.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/quick-start.html 2005-10-16 17:19:10 UTC (rev 222) +++ trunk/docs/quick-start.html 2005-10-16 17:20:32 UTC (rev 223) @@ -158,7 +158,7 @@ <p> =20 If you don't understand an error message, please consult -<a href=3D"docs/mc-manual.html#mc-manual.errormsgs">Explanation of error= messages from Memcheck</a> in the <a href=3D"docs/manual.html">Valgrind = User Manual</a> which has +<a href=3D"manual/mc-manual.html#mc-manual.errormsgs">Explanation of err= or messages from Memcheck</a> in the <a href=3D"manual/manual.html">Valgr= ind User Manual</a> which has examples of all the error messages Memcheck produces.</p> </div> <div class=3D"sect1" lang=3D"en"> @@ -169,7 +169,7 @@ </div> <p>Memcheck is not perfect; it occasionally produces false positives, and there are mechanisms for suppressing these (see -<a href=3D"manual/manual-core.html#manual-core.suppress">Suppressing err= ors</a> in the <a href=3D"manual.html">Valgrind User Manual</a>). +<a href=3D"manual/manual-core.html#manual-core.suppress">Suppressing err= ors</a> in the <a href=3D"manual/manual.html">Valgrind User Manual</a>). However, it is typically right 99% of the time, so you should be wary of ignoring its error messages. After all, you wouldn't ignore warning messages produced by a compiler, right?</p> @@ -185,7 +185,7 @@ <div></div> </div> <p>Please consult the <a href=3D"FAQ/">Valgrind FAQ</a> and the -<a href=3D"manual.html">Valgrind User Manual</a>, which have much more i= nformation. Note that the +<a href=3D"manual/manual.html">Valgrind User Manual</a>, which have much= more information. Note that the other tools in the Valgrind distribution can be invoked with the <tt class=3D"computeroutput">--tool</tt> option.</p> </div> |
|
From: <sv...@va...> - 2005-10-16 17:19:13
|
Author: njn Date: 2005-10-16 18:19:10 +0100 (Sun, 16 Oct 2005) New Revision: 222 Log: fix broken links Modified: trunk/docs/quick-start.html Modified: trunk/docs/quick-start.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/quick-start.html 2005-10-16 17:13:58 UTC (rev 221) +++ trunk/docs/quick-start.html 2005-10-16 17:19:10 UTC (rev 222) @@ -158,7 +158,7 @@ <p> =20 If you don't understand an error message, please consult -<a href=3D"mc-manual.html#mc-manual.errormsgs">Explanation of error mess= ages from Memcheck</a> in the <a href=3D"manual.html">Valgrind User Manua= l</a> which has +<a href=3D"docs/mc-manual.html#mc-manual.errormsgs">Explanation of error= messages from Memcheck</a> in the <a href=3D"docs/manual.html">Valgrind = User Manual</a> which has examples of all the error messages Memcheck produces.</p> </div> <div class=3D"sect1" lang=3D"en"> @@ -169,7 +169,7 @@ </div> <p>Memcheck is not perfect; it occasionally produces false positives, and there are mechanisms for suppressing these (see -<a href=3D"manual-core.html#manual-core.suppress">Suppressing errors</a>= in the <a href=3D"manual.html">Valgrind User Manual</a>). +<a href=3D"manual/manual-core.html#manual-core.suppress">Suppressing err= ors</a> in the <a href=3D"manual.html">Valgrind User Manual</a>). However, it is typically right 99% of the time, so you should be wary of ignoring its error messages. After all, you wouldn't ignore warning messages produced by a compiler, right?</p> @@ -184,7 +184,7 @@ <a name=3D"quick-start.info"></a>5.=A0More information</h2></div></div> <div></div> </div> -<p>Please consult the <a href=3D"FAQ.html">Valgrind FAQ</a> and the +<p>Please consult the <a href=3D"FAQ/">Valgrind FAQ</a> and the <a href=3D"manual.html">Valgrind User Manual</a>, which have much more i= nformation. Note that the other tools in the Valgrind distribution can be invoked with the <tt class=3D"computeroutput">--tool</tt> option.</p> |
|
From: <sv...@va...> - 2005-10-16 17:14:02
|
Author: njn Date: 2005-10-16 18:13:58 +0100 (Sun, 16 Oct 2005) New Revision: 221 Log: fix up leaf menus Modified: trunk/docs/index.html trunk/support/index.html Modified: trunk/docs/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/index.html 2005-10-16 17:02:11 UTC (rev 220) +++ trunk/docs/index.html 2005-10-16 17:13:58 UTC (rev 221) @@ -1 +1 @@ -<?php include 'download_docs.html'; ?> +<?php include 'quick-start.html'; ?> Modified: trunk/support/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/support/index.html 2005-10-16 17:02:11 UTC (rev 220) +++ trunk/support/index.html 2005-10-16 17:13:58 UTC (rev 221) @@ -1 +1 @@ -<?php include 'summary.html'; ?> +<?php include 'mailing_lists.html'; ?> |
|
From: <sv...@va...> - 2005-10-16 17:02:24
|
Author: njn Date: 2005-10-16 18:02:11 +0100 (Sun, 16 Oct 2005) New Revision: 220 Log: Fix some busted links. Modified: trunk/docs/download_docs.html trunk/downloads/current.html trunk/downloads/old.html trunk/downloads/repository.html trunk/help/contributing.html trunk/help/projects.html trunk/index.html trunk/info/developers.html trunk/info/news.html trunk/info/platforms.html trunk/support/summary.html Modified: trunk/docs/download_docs.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/download_docs.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/docs/download_docs.html 2005-10-16 17:02:11 UTC (rev 220) @@ -6,7 +6,7 @@ can browse it online via the menu above.</p> =20 <p>Older documentation is available from the source=20 -tarballs on our <a href=3D"/downloads/archive.html">archive page</a>. =20 +tarballs on our <a href=3D"/downloads/old.html">old release page</a>. =20 There are some helpful articles on the=20 <a href=3D"/gallery/press_media.html">Press / Media</a> page.</p> =20 Modified: trunk/downloads/current.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/current.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/downloads/current.html 2005-10-16 17:02:11 UTC (rev 220) @@ -6,7 +6,7 @@ For downloadable / browseable manual packages, go to the <a href=3D"/docs/download_docs.html">Documentation</a> page. For older releases, see the=20 -<a href=3D"/downloads/archive.html">Release Archive</a> page.</p> +<a href=3D"/downloads/old.html">Older Releases</a> page.</p> =20 <p>If you would like to be notified when a new valgrind release is made, you can subscribe to the Valgrind=20 Modified: trunk/downloads/old.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/old.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/downloads/old.html 2005-10-16 17:02:11 UTC (rev 220) @@ -2,7 +2,7 @@ =20 <p>Here you will find all the information and code available for past Valgrind releases. You can find more details on the current -release on our <a href=3D"/downloads/source_code.html">current releases +release on our <a href=3D"/downloads/current.html">current releases page</a>.<br /> =20 <b>Please note that the releases on this page are listed for Modified: trunk/downloads/repository.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/repository.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/downloads/repository.html 2005-10-16 17:02:11 UTC (rev 220) @@ -1,20 +1,18 @@ <h1>Source Code Repositories</h1> =20 <p>If you are looking for a stable release of the source code, -you should download it from the <a href=3D"/downloads/">downloads +you should download it from the <a href=3D"/downloads/current.html">down= loads page</a>. The rest of this page describes how to get hold of code at the leading edge of the development effort. Such code may not work properly.</p> =20 -<p>We are currently transitioning our repositories to use=20 -<a href=3D"http://subversion.tigris.org/">Subversion</a> (SVN) at -valgrind.org.<br /> +<p>The actively developed valgrind-3.0 line is in a +<a href=3D"http://subversion.tigris.org/">Subversion</a> (SVN) repositor= y +at valgrind.org.<br /> =20 -The actively developed valgrind-3.0 line is now in SVN at valgrind.org.<= br /> +The old valgrind-2.4 line, also in SVN, is hosted by kde.org, +at least for the moment.</p> =20 -The old valgrind-2.4 line continues to be kde.org, now also in SVN, at -least for the moment.</p> - <p>If you are doing any development work, please do it on the 3.0 line against the valgrind.org repository!</p> =20 Modified: trunk/help/contributing.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/help/contributing.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/help/contributing.html 2005-10-16 17:02:11 UTC (rev 220) @@ -18,7 +18,7 @@ <h3>Software Infrastructure, Code and Research</h3> If you are interested in writing code for Valgrind itself or its infrastructure, or doing research with it, please consult our -<a href=3D"/devel/projects.html">project suggestions</a> page. +<a href=3D"/help/projects.html">project suggestions</a> page. =20 <h3>Money</h3> <p>Donations are welcome, large or small. They help pay day-to-day @@ -27,16 +27,16 @@ buying new machines.</p> =20 <p>Individuals and companies can donate funds to support Valgrind by che= que -or money order. Please <a href=3D"/info/contact.html#email">contact us<= /a> +or money order. Please <a href=3D"/support/summary.html#email">contact = us</a> if you wish to donate.</p> =20 <h3>Equipment</h3> <p>Equipment donations can be very useful. If you wish to donate some -equipment, please <a href=3D"/info/contact.html#email">contact us</a> to= find +equipment, please <a href=3D"/support/summary.html#email">contact us</a>= to find out if the equipment would be useful, and if so, to arrange its transport.</p> =20 <h3>Other</h3> <p>For any other questions about these matters, please=20 -<a href=3D"/info/contact.html#email">contact us</a>.</p> +<a href=3D"/support/summary.html#email">contact us</a>.</p> =20 Modified: trunk/help/projects.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/help/projects.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/help/projects.html 2005-10-16 17:02:11 UTC (rev 220) @@ -315,7 +315,7 @@ =20 <h3>Ports to new platforms</h3> <p>If you are interested in porting Valgrind to a new platform, please -read <a href=3D"/devel/platforms.html#porting_plans">porting priorities +read <a href=3D"/info/platforms.html#porting_plans">porting priorities statement</a>. Note that porting is a big task and requires a great deal of knowledge about the targeted operating system and architecture. (Added August 27, 2005)</p> Modified: trunk/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/index.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/index.html 2005-10-16 17:02:11 UTC (rev 220) @@ -6,7 +6,7 @@ =20 =20 <h3 align=3D"center"> -Current release: <a href=3D"/downloads/source_code.html#current"><?php e= cho $config['release-version']; ?></a> +Current release: <a href=3D"/downloads/current.html#current"><?php echo = $config['release-version']; ?></a> </h3> =20 <p> </p> Modified: trunk/info/developers.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/info/developers.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/info/developers.html 2005-10-16 17:02:11 UTC (rev 220) @@ -2,7 +2,7 @@ =20 <p>The Valgrind developers are a loose-knit group of people from all over the world who contribute to Valgrind and have direct -write access to the Valgrind <code>svn tree</code>. Please feel +write access to the Valgrind repository. Please feel free to send praise, abuse, ideas, etc, to them.</p> =20 <p>If you want to become a valgrind developer, then the first Modified: trunk/info/news.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/info/news.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/info/news.html 2005-10-16 17:02:11 UTC (rev 220) @@ -34,7 +34,7 @@ available.</p></li> =20 <li><p>March 24, 2005:<br /> A new stable release,=20 - <a href=3D"/downloads/source_code.html#current">valgrind + <a href=3D"/downloads/old.html">valgrind 2.4.0</a>, is available. Relative to 2.2.0, 2.4.0 has improved thread and signal support, reduced memory consumption, and dozens of bug fixes.</p></li> @@ -49,21 +49,20 @@ </p></li> =20 <li><p>August 31, 2004:<br /> A new stable release,=20 - <a href=3D"/downloads/source_code.html#current">valgrind + <a href=3D"/downloads/old.html">valgrind 2.2.0</a>, is available. 2.2.0 brings many improvements over 2.0.0, and includes the new Massif heap-profiling tool.</p></li> =20 <li>July 18 2004:<br /> A new developer release,=20 - <a href=3D"/downloads/archive.html">valgrind 2.1.2</a>, is + <a href=3D"/downloads/old.html">valgrind 2.1.2</a>, is available. 2.1.2 fixes many bugs in 2.1.1, and includes the new Massif heap-profiling tool.</li> =20 <li>March 12 2004:<br /> A new developer release,=20 - <a href=3D"/downloads/archive.html">valgrind 2.1.1</a>,=20 + <a href=3D"/downloads/old.html">valgrind 2.1.1</a>,=20 is available.</li> =20 - <li>March 04 2004:<br /> An experimental=20 - <a href=3D"/devel/platforms.html">PowerPC port</a>=20 + <li>March 04 2004:<br /> An experimental PowerPC port is available.</li> =20 <li>February 15 2004:<br /> Valgrind CVS now includes=20 @@ -78,10 +77,10 @@ (<a href=3D"http://builder.com.com/5100-6375-5136747.html">read the int= erview</a>).</li> =20 <li>December 14 2003:<br /> A new developer release,=20 - <a href=3D"/downloads/archive.html">valgrind 2.1.0</a>, is available.</= li> + <a href=3D"/downloads/old.html">valgrind 2.1.0</a>, is available.</li> =20 <li>November 11 2003:<br /> A new stable release,=20 - <a href=3D"/downloads/archive.html">valgrind 2.0.0</a>,=20 + <a href=3D"/downloads/old.html">valgrind 2.0.0</a>,=20 is available.</li> =20 </ul> Modified: trunk/info/platforms.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/info/platforms.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/info/platforms.html 2005-10-16 17:02:11 UTC (rev 220) @@ -21,7 +21,7 @@ <p>For details of which distributions the current release (<?php echo $config['release-version']; ?>) builds and runs its regression tests on, see the=20 -<a href=3D"/downloads/source_code.html#current">release notes</a>.</p> +<a href=3D"/downloads/current.html#current">release notes</a>.</p> =20 =20 <a name=3D"old_mainline"></a><h2>Old Mainline</h2> Modified: trunk/support/summary.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/support/summary.html 2005-10-16 16:38:33 UTC (rev 219) +++ trunk/support/summary.html 2005-10-16 17:02:11 UTC (rev 220) @@ -1,6 +1,6 @@ <h1>Contact Summary</h1> =20 -<p>The easiest way to contact us is by <a href=3D"#email">email</a>. =20 +<p>The easiest way to contact us is by email. =20 Before sending email to us, <b>please ensure</b> that your issue isn't dealt with by information in the <a href=3D"/docs/FAQ/">Frequently Asked Questions</a>, or isn't best |
|
From: <sv...@va...> - 2005-10-16 16:38:40
|
Author: njn Date: 2005-10-16 17:38:33 +0100 (Sun, 16 Oct 2005) New Revision: 219 Log: Fix parse error Modified: trunk/php/menu.php Modified: trunk/php/menu.php =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/php/menu.php 2005-10-16 16:37:24 UTC (rev 218) +++ trunk/php/menu.php 2005-10-16 16:38:33 UTC (rev 219) @@ -5,15 +5,15 @@ array( 'url'=3D>'news.html', 'tag'=3D>'News' ), array( 'url'=3D>'tools.html', 'tag'=3D>'Tool Suite' ), array( 'url'=3D>'platforms.html', 'tag'=3D>'Supported Platforms' ), - array( 'url'=3D>'developers.html','tag'=3D>'The Developers' ), + array( 'url'=3D>'developers.html','tag'=3D>'The Developers' ) ); =20 $source_code =3D array( array( 'url'=3D>'current.html', 'tag'=3D>'Current Releases' ), - array( 'url'=3D>'old.html', 'tag'=3D>'Old Releases' ) + array( 'url'=3D>'old.html', 'tag'=3D>'Old Releases' ), array( 'url'=3D>'guis.html', 'tag'=3D>'Front Ends / GUIs' ), array( 'url'=3D>'variants.html', 'tag'=3D>'Variants / Patches' ), - array( 'url'=3D>'repository.html','tag'=3D>'Code Repository' ), + array( 'url'=3D>'repository.html','tag'=3D>'Code Repository' ) ); =20 $docs =3D array( @@ -36,7 +36,7 @@ ); =20 $help =3D array( - array( 'url'=3D>'contributing.html', 'tag'=3D>'Contributing' ) + array( 'url'=3D>'contributing.html', 'tag'=3D>'Contributing' ), array( 'url'=3D>'projects.html', 'tag'=3D>'Project Suggestions' ) ); =20 |
|
From: <sv...@va...> - 2005-10-16 16:37:37
|
Author: njn Date: 2005-10-16 17:37:24 +0100 (Sun, 16 Oct 2005) New Revision: 218 Log: Rearrange the main menu into a more logical set of groupings. Added: trunk/downloads/current.html trunk/downloads/guis.html trunk/downloads/old.html trunk/downloads/repository.html trunk/help/ trunk/help/contributing.html trunk/help/index.html trunk/help/projects.html trunk/info/platforms.html trunk/support/consultants.html trunk/support/summary.html Removed: trunk/devel/ trunk/downloads/archive.html trunk/downloads/source_code.html trunk/info/contact.html trunk/support/contributing.html Modified: trunk/docs/download_docs.html trunk/downloads/index.html trunk/php/menu.php trunk/support/index.html Modified: trunk/docs/download_docs.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/download_docs.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/docs/download_docs.html 2005-10-16 16:37:24 UTC (rev 218) @@ -12,7 +12,7 @@ =20 =20 =20 -<h3>Downloads</h3> +<!--<h3>Downloads</h3>--> =20 <table class=3D"green" width=3D"100%" cellspacing=3D"2" cellpadding=3D"5= " border=3D"0"> <tr> Deleted: trunk/downloads/archive.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/archive.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/downloads/archive.html 2005-10-16 16:37:24 UTC (rev 218) @@ -1,159 +0,0 @@ -<h1>Release Archive</h1> - -<p>Here you will find all the information and code available for -past Valgrind releases. You can find more details on the current -release on our <a href=3D"/downloads/source_code.html">downloads -page</a>.<br /> - -<b>Please note that the releases on this page are listed for -archaeological / historical purposes only, and are no longer -supported</b>.</p> - - -<div id=3D"release"> - - - -<div class=3D"hr_brown"><hr/></div> -<h3>Release 3.0.0</h3> - -<p><a href=3D"/downloads/valgrind-3.0.0.tar.bz2">valgrind 3.0.0 (tar.bz2= )</a>=20 -[2679Kb] - 3 August 2005.<br /> -<span class=3D"md5sum">md5: e976a343c61d9505162f595a8aeb09c1</span></p> - -<p>3.0.0 is a major overhaul of Valgrind. There have been many changes -and improvements. The most significant user visible change is that -Valgrind now supports architectures other than x86. 3.0.0 supports -both X86 and AMD64 running Linux. PPC32 on Linux is under development -but not yet usable. See the NEWS file for details of these and many -other changes.</p> - -<p>3.0.0 builds and runs its regression tests on at least the following -platforms, and probably more:</p> - -<ul> - <li>amd64 running SuSE 9.2, Fedora Core 2, 3 and 4</li> - <li>x86 running SuSE 9.1, 9.2, 9.3, RedHat 7.3, Redhat 8, Fedora Core = 4</li> -</ul> - -<p>We believe it should work on Linux distributions with kernel 2.4 or -2.6 and glibc 2.2.X or 2.3.X.</p> - - - -<div class=3D"hr_brown"><hr/></div> -<h3>valgrind-2.2.0</h3> - -<p> -<a href=3D"/downloads/archive/valgrind-2.2.0.tar.bz2">valgrind 2.2.0 (ta= r.bz2)</a> -[965Kb] - Aug 31 2004<br /> -<span class=3D"md5sum">md5: 30dc51f6fc94751b90b04af9c2e2c656</span> -</p> - -<p>Compared to the 2.0.0. stable release, 2.2.0 has much improved -signals/syscalls/threads support, works well on recent Linux -distros, improves SSE2/SSE3 support, and brings you Massif, a new -tool for investigating space use of your programs. There are -literally dozens of other improvements and refinements, and -hundreds of bug fixes, listed in the NEWS file.</p> - -<p>2.2.0 builds and runs its regression tests on: Red Hat 7.2, -7.3, 8.0, 9, Fedora Core 2, and SuSE 9.1. We believe it should -work on Linux distributions with kernel 2.4 or 2.6 and glibc -2.2.X or 2.3.X.</p> - - - - -<div class=3D"hr_brown"><hr/></div> -<h3>valgrind 2.1.1</h3> - -<p> -<a href=3D"/downloads/archive/valgrind-2.1.1.tar.bz2">valgrind 2.1.1 (ta= r.bz2)</a>=20 -[923 Kb] - Mar 12 2004<br /> -<span class=3D"md5sum">md5: 0010c3e8f054ecc633151c62044b646d</span> -</p> - -<p>2.1.1 contains some internal structural changes needed for -Valgrind's long-term future. These don't affect end-users. There -are also some useful user-visible changes.</p> - -<p>Greater isolation between Valgrind and the program being run, -so the program is less likely to inadvertently kill Valgrind by -doing wild writes.</p> - -<p>Massif: a new space profiling tool. Try it! It's cool, and -it'll tell you in detail where and when your C/C++ code is -allocating heap. Draws pretty .ps pictures of memory use against -time. A potentially powerful tool for making sense of your -program's space use.</p> - -<p>Fixes for many bugs, including support for more SSE2/SSE3 -instructions, various signal/syscall things, and various problems -with debug info readers.</p> - -<p>Support for glibc-2.3.3 based systems.</p> - -<p>We are now doing automatic overnight build-and-test runs on a -variety of distros. As a result, we believe 2.1.1 builds and runs -on: Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 1, SuSE 8.2, SuSE -9.</p> - - - - -<div class=3D"hr_brown"><hr/></div> -<h3>valgrind 2.1.0</h3> - -<p> -<a href=3D"/downloads/archive/valgrind-2.1.0.tar.bz2">valgrind 2.1.0 (ta= r.bz2)</a>=20 -[762 Kb] - Dec 14 2003<br /> -<span class=3D"md5sum">md5: 3e4056dd45163a5f555a23ced2f95191</span> -</p> - -<p>2.1.0 brings an overhaul of syscall and signal handling, -giving much better behaviour, especially in threaded code. 2.1.0 -can also check for file descriptor leakage. A few more SSE/SSE2 -instructions are implemented, and various reported bugs have been -fixed. See the NEWS file in the distro for more details.</p> - -<p>2.1.0 is known to compile and work on: SuSE 9, 8.2, RedHat 8, -7.3, Debian Sid. Probably works on RedHat 9, although we have not -had explicit confirmation of that yet.</p> - - - - -<div class=3D"hr_brown"><hr/></div> -<h3>valgrind 2.0.0</h3> - -<p> -<a href=3D"/downloads/archive/valgrind-2.0.0.tar.bz2">valgrind 2.0.0 (ta= r.bz2)</a>=20 -[710Kb] - Nov 11 2003<br /> -<span class=3D"md5sum">md5: 1f6a90d0ca494fb75eaeef498e8252b5</span> -</p> - -<p>Compared to the previous stable release (20031012), 2.0.0 -improves SSE/SSE2 support, fixes some minor bugs, and improves -support for SuSE 9 and the Red Hat "Severn" beta.</p> - -<p>valgrind-2.0.0 is known to build and work well on: Red Hat -7.3, 8, 9, SuSE 8.2, SuSE 9.0.</p> - -<p>See the NEWS file for more details; the ChangeLog for a -complete list of changes, or the README for more information on -this release.</p> - - - - -<div class=3D"hr_brown"><hr/></div> -<h3>valgrind 1.9.6</h3> - -<p> -<a href=3D"/downloads/archive/valgrind-1.9.6.tar.bz2">valgrind 1.9.6 (ta= r.bz2)</a>=20 -[660Kb] - May 05 2003 -</p> - - -</div> \ No newline at end of file Copied: trunk/downloads/current.html (from rev 217, trunk/downloads/sourc= e_code.html) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/source_code.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/downloads/current.html 2005-10-16 16:37:24 UTC (rev 218) @@ -0,0 +1,89 @@ +<h1>Current Releases</h1> + + +<p>The complete source code, including documentation, is +available as a tarball for the current releases. =20 +For downloadable / browseable manual packages, go to +the <a href=3D"/docs/download_docs.html">Documentation</a> page. +For older releases, see the=20 +<a href=3D"/downloads/archive.html">Release Archive</a> page.</p> + +<p>If you would like to be notified when a new valgrind release is +made, you can subscribe to the Valgrind=20 +<a href=3D"/support/mailing_lists.html#vg-announce">announcements</a> +mailing list.</p> + + + +<div class=3D"hr_brown"><hr/></div> + +<div id=3D"release"> + +<a name=3D"current"></a> + +<h3>Release 3.0.1</h3> + +<p><a href=3D"/downloads/valgrind-3.0.1.tar.bz2">valgrind 3.0.1 (tar.bz2= )</a>=20 +[2688Kb] - 29 August 2005. For x86-linux and amd64-linux.<br /> +<span class=3D"md5sum">md5: c29efdb7d1a93440f5644a6769054681</span></p> + +<p>August 29 2005: Valgrind 3.0.1 +fixes a significant number of bugs in 3.0.0, some of them critical. +If you use/distribute 3.0.0, an upgrade to 3.0.1 is recommended. See +<a href=3D"/info/release-notes-3.0.1.txt">here</a> for the 3.0.1 +release notes. +</p> + +<p>3.0.1 builds and runs its regression tests on at least the following +platforms, and probably more:</p> + +<ul> + <li>amd64 running SuSE 9.2, Fedora Core 4</li> + <li>x86 running SuSE 9.1, 9.2, 9.3, Fedora Core 4</li> +</ul> + +<p>We believe it should work on Linux distributions with kernel 2.4 or +2.6 and glibc 2.2.X or 2.3.X.</p> + + + +<h3>Release 2.4.1</h3> + +<p><a href=3D"/downloads/valgrind-2.4.1.tar.bz2">valgrind 2.4.1 (tar.bz2= )</a>=20 +[1078Kb] - 1 August 2005. For x86-linux only.<br /> +<span class=3D"md5sum">md5: 8ada0f37ddd940032b85ea859fedb037</span> +</p> + +<p>2.4.1 is a maintenance release that contains various bug fixes +which have accumulated since 2.4.0 was released about four months ago. +See the NEWS file for details. +</p> + +<p>2.4.1 builds and runs its regression tests on: Red Hat 7.3, Fedora +Core 4, SuSE 9.1 and 9.3. We believe it should work on Linux +distributions with kernel 2.4 or 2.6 and glibc 2.2.X or 2.3.X.</p> + +</div> + + + +<div class=3D"hr_brown"><hr/></div> + +<h3>RPMs / Binaries</h3> + +<p>We do not distribute binaries or RPMs. The releases available +on this website contain the source code and have to be compiled +in order to be installed on your system. Many Linux +distributions come with valgrind these days, so if you do not +want to compile your own, go to your distribution's download +site.</p> + + + +<h3>System Requirements</h3> + +<p>Programs running under Valgrind run significantly more slowly, and +use much more memory -- e.g. more than twice as much as normal under +the Memcheck tool. Therefore, it's best to use Valgrind on the most +capable machine you can get your hands on. +</p> Copied: trunk/downloads/guis.html (from rev 217, trunk/devel/guis.html) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/devel/guis.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/downloads/guis.html 2005-10-16 16:37:24 UTC (rev 218) @@ -0,0 +1,40 @@ +<h1>Graphical User Interfaces</h1> + +<p>One of the most asked for features for Valgrind is a graphical +user interface to help with configuration and use. +Several graphical front-ends have been built for Valgrind. These +are the ones we know about.</p> + +<ul> + +<li><p><a href=3D"http://alleyoop.sourceforge.net/">Alleyoop</a>,=20 +by Jeffrey Stedfast.<br /> +Alleyoop is a graphical front-end using the Gtk+ widget set and +other GNOME libraries for the X-Windows environment.</p></li> + + +<li><p><a href=3D"http://gnogrind.sourceforge.net/">Gnogrind</a>, by +Gregory Kovriga.<br /> +Gnogrind is a simple graphical user interface based on GNOME and +GTK.</p></li> + + +<li><p><a href=3D"http://www.kdevelop.org">KDevelop</a>=20 +lets you use Valgrind as a plugin.</p></li> + + +<li><p><a href=3D"http://valgui.sourceforge.net/">Valgui</a>, by Eric +Estievenart.</p></li> + + +<li><p><a href=3D"http://www.open-works.co.uk/projects/valkyrie.html">Va= lkyrie</a>=20 +is a Qt-based GUI for the Valgrind 3.X line.<br /> +Valkyrie also includes an auxiliary tool which merges XML output from=20 +multiple Memcheck runs into a single XML file, and optionally displays=20 +the merged result in the GUI.</p></li> + + +</ul> + +<p> </p> +<p> </p> Modified: trunk/downloads/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/index.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/downloads/index.html 2005-10-16 16:37:24 UTC (rev 218) @@ -1 +1 @@ -<?php include 'source_code.html'; ?> +<?php include 'current.html'; ?> Copied: trunk/downloads/old.html (from rev 217, trunk/downloads/archive.h= tml) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/archive.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/downloads/old.html 2005-10-16 16:37:24 UTC (rev 218) @@ -0,0 +1,159 @@ +<h1>Old Releases</h1> + +<p>Here you will find all the information and code available for +past Valgrind releases. You can find more details on the current +release on our <a href=3D"/downloads/source_code.html">current releases +page</a>.<br /> + +<b>Please note that the releases on this page are listed for +archaeological / historical purposes only, and are no longer +supported</b>.</p> + + +<div id=3D"release"> + + + +<div class=3D"hr_brown"><hr/></div> +<h3>Release 3.0.0</h3> + +<p><a href=3D"/downloads/valgrind-3.0.0.tar.bz2">valgrind 3.0.0 (tar.bz2= )</a>=20 +[2679Kb] - 3 August 2005.<br /> +<span class=3D"md5sum">md5: e976a343c61d9505162f595a8aeb09c1</span></p> + +<p>3.0.0 is a major overhaul of Valgrind. There have been many changes +and improvements. The most significant user visible change is that +Valgrind now supports architectures other than x86. 3.0.0 supports +both X86 and AMD64 running Linux. PPC32 on Linux is under development +but not yet usable. See the NEWS file for details of these and many +other changes.</p> + +<p>3.0.0 builds and runs its regression tests on at least the following +platforms, and probably more:</p> + +<ul> + <li>amd64 running SuSE 9.2, Fedora Core 2, 3 and 4</li> + <li>x86 running SuSE 9.1, 9.2, 9.3, RedHat 7.3, Redhat 8, Fedora Core = 4</li> +</ul> + +<p>We believe it should work on Linux distributions with kernel 2.4 or +2.6 and glibc 2.2.X or 2.3.X.</p> + + + +<div class=3D"hr_brown"><hr/></div> +<h3>valgrind-2.2.0</h3> + +<p> +<a href=3D"/downloads/archive/valgrind-2.2.0.tar.bz2">valgrind 2.2.0 (ta= r.bz2)</a> +[965Kb] - Aug 31 2004<br /> +<span class=3D"md5sum">md5: 30dc51f6fc94751b90b04af9c2e2c656</span> +</p> + +<p>Compared to the 2.0.0. stable release, 2.2.0 has much improved +signals/syscalls/threads support, works well on recent Linux +distros, improves SSE2/SSE3 support, and brings you Massif, a new +tool for investigating space use of your programs. There are +literally dozens of other improvements and refinements, and +hundreds of bug fixes, listed in the NEWS file.</p> + +<p>2.2.0 builds and runs its regression tests on: Red Hat 7.2, +7.3, 8.0, 9, Fedora Core 2, and SuSE 9.1. We believe it should +work on Linux distributions with kernel 2.4 or 2.6 and glibc +2.2.X or 2.3.X.</p> + + + + +<div class=3D"hr_brown"><hr/></div> +<h3>valgrind 2.1.1</h3> + +<p> +<a href=3D"/downloads/archive/valgrind-2.1.1.tar.bz2">valgrind 2.1.1 (ta= r.bz2)</a>=20 +[923 Kb] - Mar 12 2004<br /> +<span class=3D"md5sum">md5: 0010c3e8f054ecc633151c62044b646d</span> +</p> + +<p>2.1.1 contains some internal structural changes needed for +Valgrind's long-term future. These don't affect end-users. There +are also some useful user-visible changes.</p> + +<p>Greater isolation between Valgrind and the program being run, +so the program is less likely to inadvertently kill Valgrind by +doing wild writes.</p> + +<p>Massif: a new space profiling tool. Try it! It's cool, and +it'll tell you in detail where and when your C/C++ code is +allocating heap. Draws pretty .ps pictures of memory use against +time. A potentially powerful tool for making sense of your +program's space use.</p> + +<p>Fixes for many bugs, including support for more SSE2/SSE3 +instructions, various signal/syscall things, and various problems +with debug info readers.</p> + +<p>Support for glibc-2.3.3 based systems.</p> + +<p>We are now doing automatic overnight build-and-test runs on a +variety of distros. As a result, we believe 2.1.1 builds and runs +on: Red Hat 7.2, 7.3, 8.0, 9, Fedora Core 1, SuSE 8.2, SuSE +9.</p> + + + + +<div class=3D"hr_brown"><hr/></div> +<h3>valgrind 2.1.0</h3> + +<p> +<a href=3D"/downloads/archive/valgrind-2.1.0.tar.bz2">valgrind 2.1.0 (ta= r.bz2)</a>=20 +[762 Kb] - Dec 14 2003<br /> +<span class=3D"md5sum">md5: 3e4056dd45163a5f555a23ced2f95191</span> +</p> + +<p>2.1.0 brings an overhaul of syscall and signal handling, +giving much better behaviour, especially in threaded code. 2.1.0 +can also check for file descriptor leakage. A few more SSE/SSE2 +instructions are implemented, and various reported bugs have been +fixed. See the NEWS file in the distro for more details.</p> + +<p>2.1.0 is known to compile and work on: SuSE 9, 8.2, RedHat 8, +7.3, Debian Sid. Probably works on RedHat 9, although we have not +had explicit confirmation of that yet.</p> + + + + +<div class=3D"hr_brown"><hr/></div> +<h3>valgrind 2.0.0</h3> + +<p> +<a href=3D"/downloads/archive/valgrind-2.0.0.tar.bz2">valgrind 2.0.0 (ta= r.bz2)</a>=20 +[710Kb] - Nov 11 2003<br /> +<span class=3D"md5sum">md5: 1f6a90d0ca494fb75eaeef498e8252b5</span> +</p> + +<p>Compared to the previous stable release (20031012), 2.0.0 +improves SSE/SSE2 support, fixes some minor bugs, and improves +support for SuSE 9 and the Red Hat "Severn" beta.</p> + +<p>valgrind-2.0.0 is known to build and work well on: Red Hat +7.3, 8, 9, SuSE 8.2, SuSE 9.0.</p> + +<p>See the NEWS file for more details; the ChangeLog for a +complete list of changes, or the README for more information on +this release.</p> + + + + +<div class=3D"hr_brown"><hr/></div> +<h3>valgrind 1.9.6</h3> + +<p> +<a href=3D"/downloads/archive/valgrind-1.9.6.tar.bz2">valgrind 1.9.6 (ta= r.bz2)</a>=20 +[660Kb] - May 05 2003 +</p> + + +</div> Copied: trunk/downloads/repository.html (from rev 217, trunk/devel/cvs_sv= n.html) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/devel/cvs_svn.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/downloads/repository.html 2005-10-16 16:37:24 UTC (rev 218) @@ -0,0 +1,69 @@ +<h1>Source Code Repositories</h1> + +<p>If you are looking for a stable release of the source code, +you should download it from the <a href=3D"/downloads/">downloads +page</a>. The rest of this page describes how to get hold of +code at the leading edge of the development effort. Such code +may not work properly.</p> + +<p>We are currently transitioning our repositories to use=20 +<a href=3D"http://subversion.tigris.org/">Subversion</a> (SVN) at +valgrind.org.<br /> + +The actively developed valgrind-3.0 line is now in SVN at valgrind.org.<= br /> + +The old valgrind-2.4 line continues to be kde.org, now also in SVN, at +least for the moment.</p> + +<p>If you are doing any development work, please do it on the 3.0 line +against the valgrind.org repository!</p> + + +<div class=3D"hr_brown"><hr/></div> +<h2>The Valgrind-3.0 development line</h2> + +<p>If you want to browse the 3.0 repository you can use the +<a href=3D"http://svn.valgrind.org/">web interface</a>.</p> + +<p>To check out code on the 3.0 line (anonymous, read-only SVN=20 +access), do this:</p> + +<pre> + svn co svn://svn.valgrind.org/valgrind/trunk valgrind +</pre> + +<p> +To build the checked out code, follow the instructions in the +<code>README</code> file that the checkout should give you.</p> + +<p><b>Note:</b> as of October 2005, the 3.0 line works well on x86/Linux +<b>and AMD64/Linux</b>. On <b>PPC32/Linux</b> it works reasonably well +and is under active development. If you are interested in PPC32/Linux, +the code should be stable enough to be worth trying out. +</p> + + +<div class=3D"hr_brown"><hr/></div> +<h2>The old Valgrind-2.4 line</h2> + +<p>If you want to browse the 2.4 repository you can use the=20 +<a href=3D"http://websvn.kde.org/trunk/valgrind/">web interface</a>.</p> + +<p>To check out code on the 2.4 line (anonymous, read-only Subversion +access), follow these=20 +<a href=3D"http://developer.kde.org/source/anonsvn.html">anonymous +SVN</a> instructions. <br /> + +Or, if you want the short version, to check out the SVN trunk, run:</p> + +<pre> + svn co svn://anonsvn.kde.org/home/kde/trunk/valgrind/ +</pre> + +<p> +To build the checked out code, follow the instructions in the +<code>README</code> file that the checkout should give you.</p> + + + + Deleted: trunk/downloads/source_code.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/downloads/source_code.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/downloads/source_code.html 2005-10-16 16:37:24 UTC (rev 218) @@ -1,89 +0,0 @@ -<h1>Downloads</h1> - - -<p>The complete source code, including documentation, is -available as a tarball for the current releases. =20 -For downloadable / browseable manual packages, go to -the <a href=3D"/docs/download_docs.html">Documentation</a> page. -For older releases, see the=20 -<a href=3D"/downloads/archive.html">Release Archive</a> page.</p> - -<p>If you would like to be notified when a new valgrind release is -made, you can subscribe to the Valgrind=20 -<a href=3D"/support/mailing_lists.html#vg-announce">announcements</a> -mailing list.</p> - - - -<div class=3D"hr_brown"><hr/></div> - -<div id=3D"release"> - -<a name=3D"current"></a> - -<h3>Release 3.0.1</h3> - -<p><a href=3D"/downloads/valgrind-3.0.1.tar.bz2">valgrind 3.0.1 (tar.bz2= )</a>=20 -[2688Kb] - 29 August 2005. For x86-linux and amd64-linux.<br /> -<span class=3D"md5sum">md5: c29efdb7d1a93440f5644a6769054681</span></p> - -<p>August 29 2005: Valgrind 3.0.1 -fixes a significant number of bugs in 3.0.0, some of them critical. -If you use/distribute 3.0.0, an upgrade to 3.0.1 is recommended. See -<a href=3D"/info/release-notes-3.0.1.txt">here</a> for the 3.0.1 -release notes. -</p> - -<p>3.0.1 builds and runs its regression tests on at least the following -platforms, and probably more:</p> - -<ul> - <li>amd64 running SuSE 9.2, Fedora Core 4</li> - <li>x86 running SuSE 9.1, 9.2, 9.3, Fedora Core 4</li> -</ul> - -<p>We believe it should work on Linux distributions with kernel 2.4 or -2.6 and glibc 2.2.X or 2.3.X.</p> - - - -<h3>Release 2.4.1</h3> - -<p><a href=3D"/downloads/valgrind-2.4.1.tar.bz2">valgrind 2.4.1 (tar.bz2= )</a>=20 -[1078Kb] - 1 August 2005. For x86-linux only.<br /> -<span class=3D"md5sum">md5: 8ada0f37ddd940032b85ea859fedb037</span> -</p> - -<p>2.4.1 is a maintenance release that contains various bug fixes -which have accumulated since 2.4.0 was released about four months ago. -See the NEWS file for details. -</p> - -<p>2.4.1 builds and runs its regression tests on: Red Hat 7.3, Fedora -Core 4, SuSE 9.1 and 9.3. We believe it should work on Linux -distributions with kernel 2.4 or 2.6 and glibc 2.2.X or 2.3.X.</p> - -</div> - - - -<div class=3D"hr_brown"><hr/></div> - -<h3>RPMs / Binaries</h3> - -<p>We do not distribute binaries or RPMs. The releases available -on this website contain the source code and have to be compiled -in order to be installed on your system. Many Linux -distributions come with valgrind these days, so if you do not -want to compile your own, go to your distribution's download -site.</p> - - - -<h3>System Requirements</h3> - -<p>Programs running under Valgrind run significantly more slowly, and -use much more memory -- e.g. more than twice as much as normal under -the Memcheck tool. Therefore, it's best to use Valgrind on the most -capable machine you can get your hands on. -</p> Copied: trunk/help/contributing.html (from rev 217, trunk/support/contrib= uting.html) Added: trunk/help/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/help/index.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/help/index.html 2005-10-16 16:37:24 UTC (rev 218) @@ -0,0 +1 @@ +<?php include 'contributing.html'; ?> Copied: trunk/help/projects.html (from rev 217, trunk/devel/projects.html= ) Deleted: trunk/info/contact.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/info/contact.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/info/contact.html 2005-10-16 16:37:24 UTC (rev 218) @@ -1,53 +0,0 @@ -<h1>Contact Information</h1> - -<p>The easiest way to contact us is by <a href=3D"#email">email</a>. =20 -Before sending email to us, <b>please ensure</b> that your issue -isn't dealt with by information in the <a -href=3D"/docs/FAQ/">Frequently Asked Questions</a>, or isn't best -addressed by one of the following:</p> - - -<dl class=3D"spaced"> - -<dt>Submitting patches:</dt> -<dd>If you'd like to contribute a patch, please use our=20 -<?php echo vglink('vgbugsreport'); ?> page.</dd> - -<dt>Bug reports:</dt> -<dd>Please see the=20 -<a href=3D"/support/bug_reports.html">Bug Reports</a> page.</dd> - -<dt>Feature Requests:</dt> -<dd>Please see the=20 -<a href=3D"/support/features.html">Feature Requests</a> -page.</dd> - -<dt>Technical Support Requests:</dt>=20 -<dd>If you want to ask a question about how Valgrind works, -please use the <?php echo vglink('vgusers'); ?> mailing -list.</dd> - -<dt>Donations:</dt> -<dd>If you are interested in donating funds or equipment to -Valgrind, please send email to <?php echo vgemail('valgrind'); ?>. -</dd> - -<dt>Feedback:</dt> -<dd>If you would like to give us detailed, general feedback, -please fill out our <a href=3D"/gallery/surveys.html">survey</a>.</dd> - -<dt>Press inquiries:</dt> -<dd>Please send email to <?php echo vgemail('valgrind'); ?></dd> - -<dt>Website:</dt> -<dd>If you have found a problem on one of our pages, such as a -broken link or some incorrect information, please contact=20 -<?php echo vgemail('website'); ?>.</dd> - - -<dt><a name=3D"email"></a>Email:</dt> -<dd>The main non-technical contact address for Valgrind is: -<?php echo vgemail('valgrind'); ?>.</dd> - - -</dl> Copied: trunk/info/platforms.html (from rev 217, trunk/devel/platforms.ht= ml) Modified: trunk/php/menu.php =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/php/menu.php 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/php/menu.php 2005-10-16 16:37:24 UTC (rev 218) @@ -4,40 +4,40 @@ array( 'url'=3D>'about.html', 'tag'=3D>'About' ), array( 'url'=3D>'news.html', 'tag'=3D>'News' ), array( 'url'=3D>'tools.html', 'tag'=3D>'Tool Suite' ), + array( 'url'=3D>'platforms.html', 'tag'=3D>'Supported Platforms' ), array( 'url'=3D>'developers.html','tag'=3D>'The Developers' ), - array( 'url'=3D>'contact.html', 'tag'=3D>'Contact' ) ); =20 -$dloads =3D array( - array( 'url'=3D>'source_code.html', 'tag'=3D>'Source Code' ), - array( 'url'=3D>'variants.html', 'tag'=3D>'Variants / Patches' ), - array( 'url'=3D>'archive.html', 'tag'=3D>'Release Archive' ) +$source_code =3D array( + array( 'url'=3D>'current.html', 'tag'=3D>'Current Releases' ), + array( 'url'=3D>'old.html', 'tag'=3D>'Old Releases' ) + array( 'url'=3D>'guis.html', 'tag'=3D>'Front Ends / GUIs' ), + array( 'url'=3D>'variants.html', 'tag'=3D>'Variants / Patches' ), + array( 'url'=3D>'repository.html','tag'=3D>'Code Repository' ), ); =20 $docs =3D array( - array( 'url'=3D>'quick-start.html', 'tag'=3D>'Quick Start' ), - array( 'url'=3D>'FAQ/', 'tag'=3D>'FAQ' ), - array( 'url'=3D>'manual/manual.html', 'tag'=3D>'User Manual' ), - array( 'url'=3D>'download_docs.html', 'tag'=3D>'Download Manual' ), - array( 'url'=3D>'pubs.html', 'tag'=3D>'Publications' ) - /*array( 'url'=3D>'bookset/mc-tech.html', 'tag'=3D>'Technical' ),*/ - /*array( 'url'=3D>'manual/distro.html', 'tag'=3D>'Release Docs' ),*/ - /*array( 'url'=3D>'mini-tut.html', 'tag'=3D>'Mini-Tutorial' ),*/ + array( 'url'=3D>'quick-start.html', 'tag'=3D>'Quick Start' ), + array( 'url'=3D>'FAQ/', 'tag'=3D>'FAQ' ), + array( 'url'=3D>'manual/manual.html', 'tag'=3D>'User Manual' ), + array( 'url'=3D>'download_docs.html', 'tag'=3D>'Download Manual' ), + array( 'url'=3D>'pubs.html', 'tag'=3D>'Publications' ) + /*array( 'url'=3D>'bookset/mc-tech.html', 'tag'=3D>'Technical' ),*/ + /*array( 'url'=3D>'manual/distro.html', 'tag'=3D>'Release Docs' ),*/ + /*array( 'url'=3D>'mini-tut.html', 'tag'=3D>'Mini-Tutorial' ),*/ ); =20 -$support =3D array(=20 +$contact =3D array(=20 array( 'url'=3D>'mailing_lists.html', 'tag'=3D>'Mailing Lists' ), array( 'url'=3D>'bug_reports.html', 'tag'=3D>'Bug Reports' ), array( 'url'=3D>'features.html', 'tag'=3D>'Feature Requests' ), - array( 'url'=3D>'contributing.html', 'tag'=3D>'Contributing' ) + array( 'url'=3D>'summary.html', 'tag'=3D>'Contact Summary' ) + /*array( 'url'=3D>'consultants.html', 'tag'=3D>'Commercial Support' )*= / ); =20 -$devel =3D array( - array( 'url'=3D>'platforms.html', 'tag'=3D>'Supported Platforms' ), - array( 'url'=3D>'cvs_svn.html', 'tag'=3D>'Code Repository' ), - array( 'url'=3D>'guis.html', 'tag'=3D>'Front Ends / GUIs' ), - array( 'url'=3D>'projects.html', 'tag'=3D>'Project Suggestions' ) - /*array( 'url'=3D>'consultants.html', 'tag'=3D>'Commercial Support' )= */ +$help =3D array( + array( 'url'=3D>'contributing.html', 'tag'=3D>'Contributing' ) + array( 'url'=3D>'projects.html', 'tag'=3D>'Project Suggestions' ) ); =20 $gallery =3D array( @@ -52,10 +52,10 @@ =20 $vgdirs =3D array( 'info' =3D> array( 'url'=3D>'/info/', 'tag'=3D>'Information', = 'files'=3D>$info ), -'downloads' =3D> array( 'url'=3D>'/downloads/', 'tag'=3D>'Downloads', = 'files'=3D>$dloads ), +'downloads' =3D> array( 'url'=3D>'/downloads/', 'tag'=3D>'Source Code', = 'files'=3D>$source_code ), 'docs' =3D> array( 'url'=3D>'/docs/', 'tag'=3D>'Documentation'= , 'files'=3D>$docs ), -'support' =3D> array( 'url'=3D>'/support/', 'tag'=3D>'Support', = 'files'=3D>$support), -'devel' =3D> array( 'url'=3D>'/devel/', 'tag'=3D>'Development', = 'files'=3D>$devel ), +'support' =3D> array( 'url'=3D>'/support/', 'tag'=3D>'Contact', = 'files'=3D>$contact), +'help' =3D> array( 'url'=3D>'/help/', 'tag'=3D>'How to Help', = 'files'=3D>$help ), 'gallery' =3D> array( 'url'=3D>'/gallery/', 'tag'=3D>'Gallery', = 'files'=3D>$gallery) ); =20 Copied: trunk/support/consultants.html (from rev 217, trunk/devel/consult= ants.html) Deleted: trunk/support/contributing.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/support/contributing.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/support/contributing.html 2005-10-16 16:37:24 UTC (rev 218) @@ -1,42 +0,0 @@ -<h1>Contributing to Valgrind</h1> - -<p>If you would like to contribute to Valgrind's development, there are = a -number of ways you can help.</p> - -<h3>Bug Reports</h3> -<p>Bug reports are good. Good bug reports are even better. They should= be -submitted to our Bugzilla site (instructions are=20 -<a href=3D"/support/bug_reports.html">here</a>). Please follow the guid= elines -about writing good bug reports. Small sample programs that exhibit a bu= g -are particularly helpful.</p> - -<h3>Documentation</h3> -</p>Valgrind's documentation is not always kept up to date. Any documen= tation -patches that help in this respect are welcome. Please send them to the -<?php echo vglink( 'vgdevel' ); ?> list.</p> - -<h3>Software Infrastructure, Code and Research</h3> -If you are interested in writing code for Valgrind itself or its -infrastructure, or doing research with it, please consult our -<a href=3D"/devel/projects.html">project suggestions</a> page. - -<h3>Money</h3> -<p>Donations are welcome, large or small. They help pay day-to-day -running costs, such as bandwidth, web-hosting, electricity, and hardware -maintenance, as well as helping with larger one-off costs such as -buying new machines.</p> - -<p>Individuals and companies can donate funds to support Valgrind by che= que -or money order. Please <a href=3D"/info/contact.html#email">contact us<= /a> -if you wish to donate.</p> - -<h3>Equipment</h3> -<p>Equipment donations can be very useful. If you wish to donate some -equipment, please <a href=3D"/info/contact.html#email">contact us</a> to= find -out if the equipment would be useful, and if so, to arrange its -transport.</p> - -<h3>Other</h3> -<p>For any other questions about these matters, please=20 -<a href=3D"/info/contact.html#email">contact us</a>.</p> - Modified: trunk/support/index.html =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/support/index.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/support/index.html 2005-10-16 16:37:24 UTC (rev 218) @@ -1 +1 @@ -<?php include 'mailing_lists.html'; ?> +<?php include 'summary.html'; ?> Copied: trunk/support/summary.html (from rev 217, trunk/info/contact.html= ) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/info/contact.html 2005-10-15 17:58:03 UTC (rev 217) +++ trunk/support/summary.html 2005-10-16 16:37:24 UTC (rev 218) @@ -0,0 +1,53 @@ +<h1>Contact Summary</h1> + +<p>The easiest way to contact us is by <a href=3D"#email">email</a>. =20 +Before sending email to us, <b>please ensure</b> that your issue +isn't dealt with by information in the <a +href=3D"/docs/FAQ/">Frequently Asked Questions</a>, or isn't best +addressed by one of the following:</p> + + +<dl class=3D"spaced"> + +<dt>Submitting patches:</dt> +<dd>If you'd like to contribute a patch, please use our=20 +<?php echo vglink('vgbugsreport'); ?> page.</dd> + +<dt>Bug reports:</dt> +<dd>Please see the=20 +<a href=3D"/support/bug_reports.html">Bug Reports</a> page.</dd> + +<dt>Feature Requests:</dt> +<dd>Please see the=20 +<a href=3D"/support/features.html">Feature Requests</a> +page.</dd> + +<dt>Technical Support Requests:</dt>=20 +<dd>If you want to ask a question about how Valgrind works, +please use the <?php echo vglink('vgusers'); ?> mailing +list.</dd> + +<dt>Donations:</dt> +<dd>If you are interested in donating funds or equipment to +Valgrind, please send email to <?php echo vgemail('valgrind'); ?>. +</dd> + +<dt>Feedback:</dt> +<dd>If you would like to give us detailed, general feedback, +please fill out our <a href=3D"/gallery/surveys.html">survey</a>.</dd> + +<dt>Press inquiries:</dt> +<dd>Please send email to <?php echo vgemail('valgrind'); ?></dd> + +<dt>Website:</dt> +<dd>If you have found a problem on one of our pages, such as a +broken link or some incorrect information, please contact=20 +<?php echo vgemail('website'); ?>.</dd> + + +<dt><a name=3D"email"></a>Email:</dt> +<dd>The main non-technical contact address for Valgrind is: +<?php echo vgemail('valgrind'); ?>.</dd> + + +</dl> |
|
From: <sv...@va...> - 2005-10-16 13:52:56
|
Author: tom
Date: 2005-10-16 14:52:50 +0100 (Sun, 16 Oct 2005)
New Revision: 4938
Log:
Removed remaining traces of address space padding technology as it
is not longer relevant with the new address space manager.
Modified:
trunk/coregrind/m_syswrap/syswrap-main.c
Modified: trunk/coregrind/m_syswrap/syswrap-main.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/coregrind/m_syswrap/syswrap-main.c 2005-10-16 00:17:37 UTC (rev=
4937)
+++ trunk/coregrind/m_syswrap/syswrap-main.c 2005-10-16 13:52:50 UTC (rev=
4938)
@@ -722,7 +722,6 @@
/* Syscall may block, so run it asynchronously */
vki_sigset_t mask;
=20
-// vg_assert(!(sci->flags & PadAddr));
PRINT(" --> [async] ... \n");
=20
mask =3D tst->sig_mask;
@@ -769,9 +768,6 @@
guest state. Indeed doing so could be construed as
incorrect. */
=20
-// if (sci->flags & PadAddr)
-// VG_(pad_address_space)(VG_(client_end));
-
SysRes sres=20
=3D VG_(do_syscall6)(sysno, sci->args.arg1, sci->args.arg2,=20
sci->args.arg3, sci->args.arg4,=20
@@ -891,13 +887,6 @@
VG_TDICT_CALL(tool_post_syscall, tid, sysno, res);
}
=20
-//zz if (flags & PadAddr) {
-//zz vg_assert(!mayBlock);
-//zz VG_(unpad_address_space)(VG_(client_end));
-//zz //VG_(sanity_check_memory)();
-//zz }
-//zz=20
-
/* The syscall is done. */
sci->status.what =3D SsIdle;
=20
|
|
From: <js...@ac...> - 2005-10-16 05:18:10
|
Nightly build on phoenix ( SuSE 9.1 ) started at 2005-10-16 03:30:00 BST 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 == 200 tests, 2 stderr failures, 0 stdout failures ================= none/tests/faultstatus (stderr) none/tests/x86/int (stderr) ================================================= == 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 == 200 tests, 3 stderr failures, 0 stdout failures ================= none/tests/faultstatus (stderr) none/tests/shell (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Oct 16 03:40:09 2005 --- new.short Sun Oct 16 03:49:53 2005 *************** *** 10,14 **** ! == 200 tests, 3 stderr failures, 0 stdout failures ================= none/tests/faultstatus (stderr) - none/tests/shell (stderr) none/tests/x86/int (stderr) --- 10,13 ---- ! == 200 tests, 2 stderr failures, 0 stdout failures ================= none/tests/faultstatus (stderr) none/tests/x86/int (stderr) |
|
From: Tom H. <to...@co...> - 2005-10-16 02:40:30
|
Nightly build on dunsmere ( athlon, Fedora Core 4 ) started at 2005-10-16 03:30: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 == 202 tests, 10 stderr failures, 4 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/map_unmap (stdout) none/tests/map_unmap (stderr) none/tests/mremap2 (stdout) none/tests/sigstackgrowth (stdout) none/tests/sigstackgrowth (stderr) none/tests/stackgrowth (stdout) none/tests/stackgrowth (stderr) none/tests/x86/int (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 == 202 tests, 13 stderr failures, 4 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/gxx304 (stderr) none/tests/map_unmap (stdout) none/tests/map_unmap (stderr) none/tests/mremap2 (stdout) none/tests/shell (stderr) none/tests/sigstackgrowth (stdout) none/tests/sigstackgrowth (stderr) none/tests/stackgrowth (stdout) none/tests/stackgrowth (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Oct 16 03:35:23 2005 --- new.short Sun Oct 16 03:40:27 2005 *************** *** 8,12 **** ! == 202 tests, 13 stderr failures, 4 stdout failures ================= memcheck/tests/leak-tree (stderr) - memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) --- 8,11 ---- ! == 202 tests, 10 stderr failures, 4 stdout failures ================= memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) *************** *** 16,18 **** none/tests/faultstatus (stderr) - none/tests/gxx304 (stderr) none/tests/map_unmap (stdout) --- 15,16 ---- *************** *** 20,22 **** none/tests/mremap2 (stdout) - none/tests/shell (stderr) none/tests/sigstackgrowth (stdout) --- 18,19 ---- |
|
From: Tom H. <th...@cy...> - 2005-10-16 02:28:18
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2005-10-16 03:15: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 == 201 tests, 16 stderr failures, 1 stdout failure ================= memcheck/tests/addressable (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (stderr) memcheck/tests/nanoleak (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) none/tests/faultstatus (stderr) none/tests/x86/int (stderr) none/tests/x86/yield (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 == 201 tests, 17 stderr failures, 1 stdout failure ================= memcheck/tests/addressable (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (stderr) memcheck/tests/nanoleak (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) none/tests/faultstatus (stderr) none/tests/shell (stderr) none/tests/x86/int (stderr) none/tests/x86/yield (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Oct 16 03:21:51 2005 --- new.short Sun Oct 16 03:28:13 2005 *************** *** 8,10 **** ! == 201 tests, 17 stderr failures, 1 stdout failure ================= memcheck/tests/addressable (stderr) --- 8,10 ---- ! == 201 tests, 16 stderr failures, 1 stdout failure ================= memcheck/tests/addressable (stderr) *************** *** 24,26 **** none/tests/faultstatus (stderr) - none/tests/shell (stderr) none/tests/x86/int (stderr) --- 24,25 ---- |
|
From: Tom H. <th...@cy...> - 2005-10-16 02:25:15
|
Nightly build on ginetta ( i686, Red Hat 8.0 ) started at 2005-10-16 03:10:05 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 == 201 tests, 4 stderr failures, 0 stdout failures ================= memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/x86/int (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 == 201 tests, 5 stderr failures, 0 stdout failures ================= memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/shell (stderr) none/tests/x86/int (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Oct 16 03:19:03 2005 --- new.short Sun Oct 16 03:25:10 2005 *************** *** 8,10 **** ! == 201 tests, 5 stderr failures, 0 stdout failures ================= memcheck/tests/mempool (stderr) --- 8,10 ---- ! == 201 tests, 4 stderr failures, 0 stdout failures ================= memcheck/tests/mempool (stderr) *************** *** 12,14 **** none/tests/faultstatus (stderr) - none/tests/shell (stderr) none/tests/x86/int (stderr) --- 12,13 ---- |
|
From: Tom H. <th...@cy...> - 2005-10-16 02:22:33
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2005-10-16 03:00:03 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 == 176 tests, 8 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) memcheck/tests/strchr (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/xml1 (stderr) none/tests/as_mmap (stderr) none/tests/as_shm (stdout) none/tests/as_shm (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) 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 == 176 tests, 9 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) memcheck/tests/strchr (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/xml1 (stderr) none/tests/as_mmap (stderr) none/tests/as_shm (stdout) none/tests/as_shm (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_fcntl (stderr) none/tests/shell (stderr) none/tests/tls (stdout) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Oct 16 03:09:26 2005 --- new.short Sun Oct 16 03:22:24 2005 *************** *** 8,10 **** ! == 176 tests, 9 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) --- 8,10 ---- ! == 176 tests, 8 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) *************** *** 18,20 **** none/tests/fdleak_fcntl (stderr) - none/tests/shell (stderr) none/tests/tls (stdout) --- 18,19 ---- |
|
From: Tom H. <th...@cy...> - 2005-10-16 02:20:56
|
Nightly build on dellow ( x86_64, Fedora Core 4 ) started at 2005-10-16 03:10:05 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 == 176 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) memcheck/tests/strchr (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/xml1 (stderr) none/tests/as_mmap (stderr) none/tests/as_shm (stdout) none/tests/as_shm (stderr) none/tests/faultstatus (stderr) none/tests/mremap2 (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 176 tests, 8 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) memcheck/tests/strchr (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/xml1 (stderr) none/tests/as_mmap (stderr) none/tests/as_shm (stdout) none/tests/as_shm (stderr) none/tests/faultstatus (stderr) none/tests/mremap2 (stdout) none/tests/shell (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Oct 16 03:17:00 2005 --- new.short Sun Oct 16 03:20:52 2005 *************** *** 8,10 **** ! == 176 tests, 8 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) --- 8,10 ---- ! == 176 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) *************** *** 18,20 **** none/tests/mremap2 (stdout) - none/tests/shell (stderr) --- 18,19 ---- |
|
From: Tom H. <th...@cy...> - 2005-10-16 02:18:21
|
Nightly build on aston ( x86_64, Fedora Core 3 ) started at 2005-10-16 03:05:09 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 == 176 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) memcheck/tests/strchr (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/xml1 (stderr) none/tests/as_mmap (stderr) none/tests/as_shm (stdout) none/tests/as_shm (stderr) none/tests/faultstatus (stderr) none/tests/mremap2 (stdout) ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 176 tests, 8 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) memcheck/tests/strchr (stderr) memcheck/tests/weirdioctl (stderr) memcheck/tests/xml1 (stderr) none/tests/as_mmap (stderr) none/tests/as_shm (stdout) none/tests/as_shm (stderr) none/tests/faultstatus (stderr) none/tests/mremap2 (stdout) none/tests/shell (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Sun Oct 16 03:12:58 2005 --- new.short Sun Oct 16 03:18:13 2005 *************** *** 8,10 **** ! == 176 tests, 8 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) --- 8,10 ---- ! == 176 tests, 7 stderr failures, 2 stdout failures ================= memcheck/tests/sigprocmask (stderr) *************** *** 18,20 **** none/tests/mremap2 (stdout) - none/tests/shell (stderr) --- 18,19 ---- |
|
From: <sv...@va...> - 2005-10-16 00:17:46
|
Author: njn
Date: 2005-10-16 01:17:37 +0100 (Sun, 16 Oct 2005)
New Revision: 4937
Log:
A small Cachegrind cleanup: previously it was copying some things (eg.
instr_size and instr_addr) into Ir events, then later copying those into
instrInfo nodes. Now it just allocates the instrInfo nodes earlier and
copies them in directly. This is a bit more concise and easier to
understand.
Modified:
trunk/cachegrind/cg_main.c
Modified: trunk/cachegrind/cg_main.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/cachegrind/cg_main.c 2005-10-15 22:07:28 UTC (rev 4936)
+++ trunk/cachegrind/cg_main.c 2005-10-16 00:17:37 UTC (rev 4937)
@@ -414,10 +414,10 @@
=20
typedef
struct {
- EventKind ekind;
- Int size; /* ALL */
- Addr64 iaddr; /* ALL. For Dr/Dw/Dm is & of parent insn. */
- IRAtom* dataEA; /* Dr/Dw/Dm only */ /* IR ATOM ONLY */
+ EventKind ekind; // All
+ InstrInfo* inode; // All; inode for this event's instructio=
n
+ Int datasize; // Dr/Dw/Dm only
+ IRAtom* dataEA; // Dr/Dw/Dm only; IR ATOM ONLY
}
Event;
=20
@@ -486,32 +486,24 @@
}
=20
=20
-static
-void init_InstrInfo( InstrInfo* n, Addr instr_addr, Int instr_len )
-{
- n->instr_addr =3D instr_addr;
- n->instr_len =3D instr_len;
- n->parent =3D get_lineCC(instr_addr);
-}
-
static void showEvent ( Event* ev )
{
switch (ev->ekind) {
case Event_Ir:=20
- VG_(printf)("Ir %d 0x%llx\n", ev->size, ev->iaddr);
+ VG_(printf)("Ir %p\n", ev->inode);
break;
case Event_Dr:
- VG_(printf)("Dr %d 0x%llx EA=3D", ev->size, ev->iaddr);
+ VG_(printf)("Dr %p %d EA=3D", ev->inode, ev->datasize);
ppIRExpr(ev->dataEA);=20
VG_(printf)("\n");
break;
case Event_Dw:
- VG_(printf)("Dw %d 0x%llx EA=3D", ev->size, ev->iaddr);
+ VG_(printf)("Dw %p %d EA=3D", ev->inode, ev->datasize);
ppIRExpr(ev->dataEA);=20
VG_(printf)("\n");
break;
case Event_Dm:
- VG_(printf)("Dm %d 0x%llx EA=3D", ev->size, ev->iaddr);
+ VG_(printf)("Dm %p %d EA=3D", ev->inode, ev->datasize);
ppIRExpr(ev->dataEA);=20
VG_(printf)("\n");
break;
@@ -521,29 +513,22 @@
}
}
=20
-/* Reserve InstrInfo for the first mention of a new insn. */
-
-static InstrInfo* reserve_InstrInfo ( CgState* cgs )
+// Reserve and initialise an InstrInfo for the first mention of a new in=
sn.
+static
+InstrInfo* setup_InstrInfo ( CgState* cgs, Addr instr_addr, UInt instr_l=
en )
{
InstrInfo* i_node;
tl_assert(cgs->bbInfo_i >=3D 0);
tl_assert(cgs->bbInfo_i < cgs->bbInfo->n_instrs);
i_node =3D &cgs->bbInfo->instrs[ cgs->bbInfo_i ];
+ i_node->instr_addr =3D instr_addr;
+ i_node->instr_len =3D instr_len;
+ i_node->parent =3D get_lineCC(instr_addr);
cgs->bbInfo_i++;
return i_node;
}
=20
=20
-/* Find the most recently allocated InstrInfo. */
-
-static InstrInfo* find_most_recent_InstrInfo ( CgState* cgs )
-{
- tl_assert(cgs->bbInfo_i >=3D 0);
- tl_assert(cgs->bbInfo_i <=3D cgs->bbInfo->n_instrs);
- return &cgs->bbInfo->instrs[ cgs->bbInfo_i - 1 ];
-}
-
-
/* Generate code for all outstanding memory events, and mark the queue
empty. Code is generated into cgs->bbOut, and this activity
'consumes' slots in cgs->bbInfo. */
@@ -555,12 +540,7 @@
void* helperAddr;
IRExpr** argv;
IRExpr* i_node_expr;
- IRExpr* i_node2_expr;
- IRExpr* i_node3_expr;
IRDirty* di;
- InstrInfo* i_node;
- InstrInfo* i_node2;
- InstrInfo* i_node3;
Event* ev;
Event* ev2;
Event* ev3;
@@ -586,53 +566,32 @@
showEvent( ev );
}
=20
- /* For any event we find the relevant InstrInfo. The following
- assumes that Event_Ir is the first event to refer to any
- specific insn, and so a new entry in the cgs->bbInfo->instrs
- is allocated. All other events (Dr,Dw,Dm) must refer to the
- most recently encountered IMark and so we use the
- most-recently allocated instrs[] entry, which must exist. */
+ i_node_expr =3D mkIRExpr_HWord( (HWord)ev->inode );
=20
- if (ev->ekind =3D=3D Event_Ir) {
- /* allocate an InstrInfo and fill in its addr/size. */
- i_node =3D reserve_InstrInfo( cgs );
- init_InstrInfo( i_node,
- (Addr)ev->iaddr, /* i addr */
- ev->size /* i size */);
- } else {
- /* use the most-recently allocated i_node but don't mess with
- its internals */
- i_node =3D find_most_recent_InstrInfo( cgs );
- /* it must match the declared parent instruction of this event.=
*/
- tl_assert(i_node->instr_addr =3D=3D ev->iaddr);
- }
-
- i_node_expr =3D mkIRExpr_HWord( (HWord)i_node );
-
/* Decide on helper fn to call and args to pass it, and advance
i appropriately. */
switch (ev->ekind) {
case Event_Ir:
/* Merge with a following Dr/Dm if it is from this insn. */
if (ev2 && (ev2->ekind =3D=3D Event_Dr || ev2->ekind =3D=3D =
Event_Dm)) {
- tl_assert(ev2->iaddr =3D=3D ev->iaddr);
+ tl_assert(ev2->inode =3D=3D ev->inode);
helperName =3D "log_1I_1Dr_cache_access";
helperAddr =3D &log_1I_1Dr_cache_access;
argv =3D mkIRExprVec_3( i_node_expr,
ev2->dataEA,
- mkIRExpr_HWord( ev2->size ) );
+ mkIRExpr_HWord( ev2->datasize ) );
regparms =3D 3;
i +=3D 2;
}
/* Merge with a following Dw if it is from this insn. */
else
if (ev2 && ev2->ekind =3D=3D Event_Dw) {
- tl_assert(ev2->iaddr =3D=3D ev->iaddr);
+ tl_assert(ev2->inode =3D=3D ev->inode);
helperName =3D "log_1I_1Dw_cache_access";
helperAddr =3D &log_1I_1Dw_cache_access;
argv =3D mkIRExprVec_3( i_node_expr,
ev2->dataEA,
- mkIRExpr_HWord( ev2->size ) );
+ mkIRExpr_HWord( ev2->datasize ) );
regparms =3D 3;
i +=3D 2;
}
@@ -642,20 +601,9 @@
{
helperName =3D "log_3I_0D_cache_access";
helperAddr =3D &log_3I_0D_cache_access;
-
- i_node2 =3D reserve_InstrInfo( cgs );
- init_InstrInfo( i_node2,
- (Addr)ev2->iaddr, /* i addr */
- ev2->size /* i size */);
- i_node2_expr =3D mkIRExpr_HWord( (HWord)i_node2 );
-
- i_node3 =3D reserve_InstrInfo( cgs );
- init_InstrInfo( i_node3,
- (Addr)ev3->iaddr, /* i addr */
- ev3->size /* i size */);
- i_node3_expr =3D mkIRExpr_HWord( (HWord)i_node3 );
-
- argv =3D mkIRExprVec_3( i_node_expr, i_node2_expr, i_node=
3_expr );
+ argv =3D mkIRExprVec_3( i_node_expr,=20
+ mkIRExpr_HWord( (HWord)ev2->inode )=
,=20
+ mkIRExpr_HWord( (HWord)ev3->inode )=
);
regparms =3D 3;
i +=3D 3;
}
@@ -664,14 +612,8 @@
if (ev2 && ev2->ekind =3D=3D Event_Ir) {
helperName =3D "log_2I_0D_cache_access";
helperAddr =3D &log_2I_0D_cache_access;
-
- i_node2 =3D reserve_InstrInfo( cgs );
- init_InstrInfo( i_node2,
- (Addr)ev2->iaddr, /* i addr */
- ev2->size /* i size */);
-
- i_node2_expr =3D mkIRExpr_HWord( (HWord)i_node2 );
- argv =3D mkIRExprVec_2( i_node_expr, i_node2_expr );
+ argv =3D mkIRExprVec_2( i_node_expr,
+ mkIRExpr_HWord( (HWord)ev2->inode )=
);
regparms =3D 2;
i +=3D 2;
}
@@ -694,7 +636,7 @@
helperAddr =3D &log_0I_1Dr_cache_access;
argv =3D mkIRExprVec_3( i_node_expr,=20
ev->dataEA,=20
- mkIRExpr_HWord( ev->size ) );
+ mkIRExpr_HWord( ev->datasize ) );
regparms =3D 3;
i++;
break;
@@ -703,7 +645,7 @@
helperAddr =3D &log_0I_1Dw_cache_access;
argv =3D mkIRExprVec_3( i_node_expr,
ev->dataEA,=20
- mkIRExpr_HWord( ev->size ) );
+ mkIRExpr_HWord( ev->datasize ) );
regparms =3D 3;
i++;
break;
@@ -722,56 +664,55 @@
cgs->events_used =3D 0;
}
=20
-
-static void addEvent_Ir ( CgState* cgs, Int size, Addr64 iaddr )
+static void addEvent_Ir ( CgState* cgs, InstrInfo* inode )
{
Event* evt;
- tl_assert(size >=3D 0 && size <=3D MIN_LINE_SIZE);
if (cgs->events_used =3D=3D N_EVENTS)
flushEvents(cgs);
tl_assert(cgs->events_used >=3D 0 && cgs->events_used < N_EVENTS);
- /* If vex fails to decode an insn, the size will be zero, but that
- can't really be true -- the cpu couldn't have determined the
- insn was undecodable without looking at it. Hence: */
- if (size =3D=3D 0)
- size =3D 1;
evt =3D &cgs->events[cgs->events_used];
- evt->ekind =3D Event_Ir;
- evt->size =3D size;
- evt->iaddr =3D iaddr;
- evt->dataEA =3D NULL; /*paranoia*/
+ evt->ekind =3D Event_Ir;
+ evt->inode =3D inode;
+ evt->datasize =3D 0;
+ evt->dataEA =3D NULL; /*paranoia*/
cgs->events_used++;
}
=20
-static void addEvent_Dr ( CgState* cgs, Int size, Addr64 iaddr, IRAtom* =
ea )
+static
+void addEvent_Dr ( CgState* cgs, InstrInfo* inode, Int datasize, IRAtom*=
ea )
{
Event* evt;
tl_assert(isIRAtom(ea));
- tl_assert(size >=3D 1 && size <=3D MIN_LINE_SIZE);
+ tl_assert(datasize >=3D 1 && datasize <=3D MIN_LINE_SIZE);
if (cgs->events_used =3D=3D N_EVENTS)
flushEvents(cgs);
tl_assert(cgs->events_used >=3D 0 && cgs->events_used < N_EVENTS);
evt =3D &cgs->events[cgs->events_used];
- evt->ekind =3D Event_Dr;
- evt->size =3D size;
- evt->iaddr =3D iaddr;
- evt->dataEA =3D ea;
+ evt->ekind =3D Event_Dr;
+ evt->inode =3D inode;
+ evt->datasize =3D datasize;
+ evt->dataEA =3D ea;
cgs->events_used++;
}
=20
-static void addEvent_Dw ( CgState* cgs, Int size, Addr64 iaddr, IRAtom* =
ea )
+static
+void addEvent_Dw ( CgState* cgs, InstrInfo* inode, Int datasize, IRAtom*=
ea )
{
+ Event* lastEvt;
+ Event* evt;
+
tl_assert(isIRAtom(ea));
- tl_assert(size >=3D 1 && size <=3D MIN_LINE_SIZE);
+ tl_assert(datasize >=3D 1 && datasize <=3D MIN_LINE_SIZE);
=20
- /* Is it possible to merge this write into an immediately preceding
- read? */
+ /* Is it possible to merge this write with the preceding read? */
+ lastEvt =3D &cgs->events[cgs->events_used-1];
if (cgs->events_used > 0
- && cgs->events[cgs->events_used-1].ekind =3D=3D Event_Dr
- && cgs->events[cgs->events_used-1].size =3D=3D size
- && cgs->events[cgs->events_used-1].iaddr =3D=3D iaddr
- && eqIRAtom(cgs->events[cgs->events_used-1].dataEA, ea)) {
- cgs->events[cgs->events_used-1].ekind =3D Event_Dm;
+ && lastEvt->ekind =3D=3D Event_Dr
+ && lastEvt->datasize =3D=3D datasize
+ && lastEvt->inode =3D=3D inode
+ && eqIRAtom(lastEvt->dataEA, ea))
+ {
+ lastEvt->ekind =3D Event_Dm;
return;
}
=20
@@ -779,10 +720,11 @@
if (cgs->events_used =3D=3D N_EVENTS)
flushEvents(cgs);
tl_assert(cgs->events_used >=3D 0 && cgs->events_used < N_EVENTS);
- cgs->events[cgs->events_used].ekind =3D Event_Dw;
- cgs->events[cgs->events_used].size =3D size;
- cgs->events[cgs->events_used].iaddr =3D iaddr;
- cgs->events[cgs->events_used].dataEA =3D ea;
+ evt =3D &cgs->events[cgs->events_used];
+ evt->ekind =3D Event_Dw;
+ evt->inode =3D inode;
+ evt->datasize =3D datasize;
+ evt->dataEA =3D ea;
cgs->events_used++;
}
=20
@@ -792,11 +734,12 @@
static IRBB* cg_instrument ( IRBB* bbIn, VexGuestLayout* layout,=20
IRType gWordTy, IRType hWordTy )
{
- Int i;
+ Int i, isize;
IRStmt* st;
Addr64 cia; /* address of current insn */
CgState cgs;
IRTypeEnv* tyenv =3D bbIn->tyenv;
+ InstrInfo* curr_inode =3D NULL;
=20
=20
if (gWordTy !=3D hWordTy) {
@@ -804,9 +747,12 @@
VG_(tool_panic)("host/guest word size mismatch");
}
=20
- /* Set up BB */
- cgs.bbOut =3D emptyIRBB();
- cgs.bbOut->tyenv =3D dopyIRTypeEnv(tyenv);
+ /* Set up BB, including copying of the where-next stuff. */
+ cgs.bbOut =3D emptyIRBB();
+ cgs.bbOut->tyenv =3D dopyIRTypeEnv(tyenv);
+ tl_assert( isIRAtom(bbIn->next) );
+ cgs.bbOut->next =3D dopyIRExpr(bbIn->next);
+ cgs.bbOut->jumpkind =3D bbIn->jumpkind;
=20
// Get the first statement, and initial cia from it
i =3D 0;
@@ -823,7 +769,8 @@
if (DEBUG_CG)
VG_(printf)("\n\n---------- cg_instrument ----------\n");
=20
- // Traverse the block, adding events and flushing as necessary.
+ // Traverse the block, initialising inodes, adding events and flushin=
g as
+ // necessary.
for (i =3D 0; i < bbIn->stmts_used; i++) {
=20
st =3D bbIn->stmts[i];
@@ -838,19 +785,32 @@
break;
=20
case Ist_IMark:
- cia =3D st->Ist.IMark.addr;
- addEvent_Ir( &cgs, st->Ist.IMark.len, cia );
+ cia =3D st->Ist.IMark.addr;
+ isize =3D st->Ist.IMark.len;
+
+ // If Vex fails to decode an instruction, the size will be z=
ero.
+ // Pretend otherwise.
+ if (isize =3D=3D 0) isize =3D VG_MIN_INSTR_SZB;
+
+ // Check size. XXX: broken for client requests!
+ tl_assert(VG_MIN_INSTR_SZB <=3D isize && isize <=3D VG_MAX_I=
NSTR_SZB);
+
+ // Get space for and init the inode, record it as the curren=
t one.
+ // Subsequent Dr/Dw/Dm events from the same instruction will=
=20
+ // also use it.
+ curr_inode =3D setup_InstrInfo(&cgs, cia, isize);
+
+ addEvent_Ir( &cgs, curr_inode );
break;
=20
case Ist_Tmp: {
IRExpr* data =3D st->Ist.Tmp.data;
if (data->tag =3D=3D Iex_Load) {
IRExpr* aexpr =3D data->Iex.Load.addr;
- tl_assert( isIRAtom(aexpr) );
// Note also, endianness info is ignored. I guess
// that's not interesting.
- addEvent_Dr( &cgs, sizeofIRType(data->Iex.Load.ty),=20
- cia, aexpr );
+ addEvent_Dr( &cgs, curr_inode, sizeofIRType(data->Iex.Loa=
d.ty),=20
+ aexpr );
}
break;
}
@@ -858,10 +818,8 @@
case Ist_Store: {
IRExpr* data =3D st->Ist.Store.data;
IRExpr* aexpr =3D st->Ist.Store.addr;
- tl_assert( isIRAtom(aexpr) );
- addEvent_Dw( &cgs,=20
- sizeofIRType(typeOfIRExpr(tyenv, data)),=20
- cia, aexpr );
+ addEvent_Dw( &cgs, curr_inode,=20
+ sizeofIRType(typeOfIRExpr(tyenv, data)), aexpr =
);
break;
}
=20
@@ -869,8 +827,7 @@
Int dataSize;
IRDirty* d =3D st->Ist.Dirty.details;
if (d->mFx !=3D Ifx_None) {
- /* This dirty helper accesses memory. Collect the
- details. */
+ /* This dirty helper accesses memory. Collect the detail=
s. */
tl_assert(d->mAddr !=3D NULL);
tl_assert(d->mSize !=3D 0);
dataSize =3D d->mSize;
@@ -881,9 +838,9 @@
if (dataSize > MIN_LINE_SIZE)
dataSize =3D MIN_LINE_SIZE;
if (d->mFx =3D=3D Ifx_Read || d->mFx =3D=3D Ifx_Modify)
- addEvent_Dr( &cgs, dataSize, cia, d->mAddr );
+ addEvent_Dr( &cgs, curr_inode, dataSize, d->mAddr );
if (d->mFx =3D=3D Ifx_Write || d->mFx =3D=3D Ifx_Modify)
- addEvent_Dw( &cgs, dataSize, cia, d->mAddr );
+ addEvent_Dw( &cgs, curr_inode, dataSize, d->mAddr );
} else {
tl_assert(d->mAddr =3D=3D NULL);
tl_assert(d->mSize =3D=3D 0);
@@ -912,13 +869,8 @@
}
=20
/* At the end of the bb. Flush outstandings. */
- tl_assert(isIRAtom(bbIn->next));
flushEvents( &cgs );
=20
- /* copy where-next stuff. */
- cgs.bbOut->next =3D dopyIRExpr(bbIn->next);
- cgs.bbOut->jumpkind =3D bbIn->jumpkind;
-
/* done. stay sane ... */
tl_assert(cgs.bbInfo_i =3D=3D cgs.bbInfo->n_instrs);
=20
|