You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(19) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
1
(14) |
2
(16) |
3
(7) |
|
4
(7) |
5
(9) |
6
(8) |
7
(10) |
8
(16) |
9
(15) |
10
(9) |
|
11
(11) |
12
(13) |
13
(8) |
14
(8) |
15
(10) |
16
(25) |
17
(7) |
|
18
(7) |
19
(13) |
20
(10) |
21
(14) |
22
(11) |
23
(12) |
24
(8) |
|
25
(19) |
26
(10) |
27
(16) |
28
(13) |
|
|
|
|
From: Tomas M. <tom...@2p...> - 2007-02-01 20:41:10
|
I added --leak-check=dump which dumps of leaked memory. It may help significantly when hunting a leak when you know what is in memory. I'm sending patch agains SVN trunk. Note it's not perfect - no XML dump and maybe malloc memory should be also freed. Maybe it could help someone. I had no time to check if already has been discussed. Tomas |
|
From: <sv...@va...> - 2007-02-01 11:36:52
|
Author: de Date: 2007-02-01 11:36:45 +0000 (Thu, 01 Feb 2007) New Revision: 310 Log: Lots of updating + tidying up of bits and pieces, deletion of old irrelevancies, ... ... Modified: trunk/.htaccess trunk/admin/updating.readme trunk/downloads/current.html trunk/downloads/guis.html trunk/downloads/old.html trunk/downloads/repository.html trunk/downloads/variants.html trunk/help/projects.html trunk/index.html trunk/info/developers.html trunk/info/news.html trunk/info/platforms.html trunk/php/.htconfx trunk/php/funcs.php trunk/php/header.php Modified: trunk/.htaccess =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/.htaccess 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/.htaccess 2007-02-01 11:36:45 UTC (rev 310) @@ -1,4 +1,5 @@ # Date created: March 08 2005 +# Last updated: February 1 2007 # Note 1: See /admin/updating.readme # Note 2: There are .htaccess files in /php/ and /admin/ =20 @@ -11,7 +12,7 @@ =20 # set the include path: # this is for phoenix: -# php_value include_path "/home/de/WebPages/valgrind-www/trunk/php" +# php_value include_path "/home/de/WebSites/valgrind-www/trunk/php" # this is for exonetric: php_value include_path "/usr/local/www/sites/valgrind-www/php" =20 @@ -47,28 +48,46 @@ =20 =20 # permanent redirects for *very* frequently accessed old pages -Redirect 301 /docs/FAQ/ http://www.valgrind.org/docs/manual/FAQ.html -Redirect 301 /docs/FAQ.html http://www.valgrind.org/docs/manual/FAQ.html -Redirect 301 /docs/FAQ/FAQ.html http://www.valgrind.org/docs/manual/FAQ.= html -Redirect 301 /docs/FAQ/faq.misc.html http://www.valgrind.org/docs/manual= /FAQ.html -Redirect 301 /docs/FAQ/faq.help.html http://www.valgrind.org/docs/manual= /FAQ.html -Redirect 301 /docs/valgrind_faq.html.tar.bz2 http://www.valgrind.org/doc= s/manual/FAQ.html +Redirect 301 /docs/FAQ/faq.abort.html http://www.valgrind.org/docs/manua= l/faq.html +Redirect 301 /docs/FAQ.html http://www.valgrind.org/docs/manual/faq.html +Redirect 301 /docs/FAQ/FAQ.html http://www.valgrind.org/docs/manual/faq.= html +Redirect 301 /docs/FAQ/faq.misc.html http://www.valgrind.org/docs/manual= /faq.html +Redirect 301 /docs/FAQ/faq.help.html http://www.valgrind.org/docs/manual= /faq.html +Redirect 301 /docs/FAQ/faq.background.html http://www.valgrind.org/docs/= manual/faq.html +Redirect 301 /docs/valgrind_faq.html.tar.bz2 http://www.valgrind.org/doc= s/manual/faq.html +Redirect 301 /docs/FAQ/valgrind-FAQ.ps.bz2 http://valgrind.org/docs/manu= al/valgrind_manual.ps.bz2 +Redirect 301 /docs/FAQ/ http://www.valgrind.org/docs/manual/faq.html +# Redirect 301 /docs/quick-start.html http://www.valgrind.org/docs/manual/= QuickStart.html +Redirect 301 /docs/manual/quickstart.html http://www.valgrind.org/docs/m= anual/QuickStart.html +Redirect 301 /docs/valgrind-quick-start.html.bz2 http://valgrind.org/doc= s/manual/valgrind_manual.html.tar.bz2 +# +Redirect 301 /docs/dist.html http://www.valgrind.org/docs/manual/dist.ht= ml Redirect 301 /docs/manual.html http://www.valgrind.org/docs/manual/manua= l.html Redirect 301 /docs/mc-manual.html http://www.valgrind.org/docs/manual/mc= -manual.html Redirect 301 /docs/manual/mc_main.html http://www.valgrind.org/docs/manu= al/mc-manual.html +Redirect 301 /docs/manual/hg_main.html http://www.valgrind.org/docs/manu= al/hg-manual.html +Redirect 301 /docs/manual/hg_manual.html http://www.valgrind.org/docs/ma= nual/hg-manual.html +Redirect 301 /docs/manual/cg_techdocs.html http://valgrind.org/docs/manu= al/cg-tech-docs.html Redirect 301 /docs/manual-core.html http://www.valgrind.org/docs/manual/= manual-core.html +Redirect 301 /docs/manual/coregrind_core.html http://valgrind.org/docs/m= anual/manual.html +Redirect 301 /docs/manual/valgrind_manual.pdf.bz2 http://valgrind.org/do= cs/manual/valgrind_manual.pdf Redirect 301 /docs/bookset/mc-manual.leaks.html http://www.valgrind.org/= docs/manual/mc-manual.html#mc-manual.leaks +Redirect 301 /docs/bookset/manual-core.out2file.html http://www.valgrind= .org/docs/manual/manual-core.html # Redirect 301 /downloads.html http://www.valgrind.org/downloads/current.h= tml Redirect 301 /downloads/archive.html http://www.valgrind.org/downloads/o= ld.html Redirect 301 /downloads/source_code.html http://www.valgrind.org/downloa= ds/current.html +Redirect 301 /downloads/valgrind-2.2.0.tar.bz2 http://www.valgrind.org/d= ownloads/archive/valgrind-2.2.0.tar.bz2 Redirect 301 /downloads/valgrind-2.4.0.tar.bz2 http://www.valgrind.org/d= ownloads/archive/valgrind-2.4.0.tar.bz2 Redirect 301 /downloads/valgrind-2.4.1.tar.bz2 http://www.valgrind.org/d= ownloads/archive/valgrind-2.4.1.tar.bz2 Redirect 301 /downloads/valgrind-3.0.0.tar.bz2 http://www.valgrind.org/d= ownloads/archive/valgrind-3.0.0.tar.bz2 Redirect 301 /downloads/valgrind-3.0.1.tar.bz2 http://www.valgrind.org/d= ownloads/archive/valgrind-3.0.1.tar.bz2 # Redirect 301 /devel/guis.html http://www.valgrind.org/downloads/guis.htm= l +Redirect 301 /devel/projects.html http://www.valgrind.org/help/projects.= html +Redirect 301 /devel/cvs_svn.html http://www.valgrind.org/downloads/repos= itory.html +Redirect 301 /devel/platforms.html http://www.valgrind.org/info/platform= s.html # Redirect 301 /info/release-notes-3.0.0.txt http://www.valgrind.org/docs/= manual/dist.news.html Redirect 301 /info/release-notes-3.0.1.txt http://www.valgrind.org/docs/= manual/dist.news.html Modified: trunk/admin/updating.readme =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/admin/updating.readme 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/admin/updating.readme 2007-02-01 11:36:45 UTC (rev 310) @@ -1,4 +1,4 @@ -#!/usr/bin/perl +<!-- -*- sh -*- --> =20 ----------------------------------------------------------------------- New Release ToDo=20 @@ -9,6 +9,8 @@ de@phoenix:~/Programs$ cd valgrind/ /valgrind$ ./autogen.sh /valgrind$ ./configure --prefix=3D`pwd`/Inst +# (make install is optional) +/valgrind$ make install /valgrind$ cd ./docs/ /valgrind/docs/$ make website-docs /valgrind/docs/$ make valkyrie-docs @@ -32,14 +34,6 @@ Create a new entry in the list for the new release. Get jrs to do some 'blurb' for this. =20 -# the source tarball: -Move the previous release to the /downloads/archive/ dir. -Get a copy of the new valgrind-x.x.x.tar.bz2 tarball, and put it in -the /downloads/ dir. Generate an md5sum for it. -Do both the above 'manually' on the website: we do not keep the=20 -old tarballs in svn, so be careful not to inadvertently commit the=20 -tarballs to the repo on 'svn commit'. - # in /downloads/current.html: Move everything in "Current Release" to /downloads/old.html, then update the "Current Release" stuff. @@ -48,8 +42,17 @@ # in downloads/old.html: Edit the stuff that has just been removed from 'Current Release', removing links to eg. 'dist.news.html'. -Change the tarball-link to "/downloads/archive/valgrind-x.x.x.tar.bz2" +Change the tarball link to "/downloads/archive/valgrind-x.x.x.tar.bz2" =20 +# the source tarball: +On exonetric, move the previous tarball to the /downloads/archive/ dir. +Get a copy of the new valgrind-x.x.x.tar.bz2 tarball, and put it in +the /downloads/ dir. Generate an md5sum for it. +Note: do *not* do this via svn, as we do not keep old tarballs in the +website repo. Do both the above 'manually' on the website. +Be careful not to inadvertently commit the tarballs to the repo on=20 +'svn commit' if you do this at home. + # update the documentation: de@phoenix:~/WebPages/valgrind-www/trunk/$ cd ./docs/ /trunk/docs/$ mkdir ./manual-old 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 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/downloads/current.html 2007-02-01 11:36:45 UTC (rev 310) @@ -1,11 +1,10 @@ <h1><?php echo $curr_page['name']; ?></h1> =20 =20 -<p>The complete source code, including documentation, is -available as a tarball for the current release. =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 +<p>The complete source code, including documentation, is available as a=20 +tarball for the current release. For downloadable / browseable manual=20 +packages, go to the <a href=3D"/docs/download_docs.html">Documentation</= a>=20 +page. For older releases, see the=20 <a href=3D"/downloads/old.html">Release Archive</a> page.</p> =20 <p>If you would like to be notified when a new valgrind release is @@ -13,121 +12,41 @@ <a href=3D"/support/mailing_lists.html#vg-announce">announcements</a> mailing list.</p> =20 - - <div class=3D"hr_brown"><hr/></div> =20 + <div id=3D"release"> =20 -<a name=3D"current"></a> +<a name=3D"current"><h3>Release 3.2.3</h3></a> =20 - -<h3>Release 3.2.3</h3> - <p><a href=3D"/downloads/valgrind-3.2.3.tar.bz2">valgrind 3.2.3 (tar.bz2= )</a>=20 [4016Kb] - 29 January 2007.<br /> For {x86,amd64,ppc32,ppc64}-linux.<br /> <span class=3D"md5sum">md5: 978847992b136c8d8cb5c6559a91df1c</span></p> + <p>You may want to look at the=20 <a href=3D"/docs/manual/dist.news.html">3.2.3 release notes</a>. </p> =20 <p>3.2.3 is almost identical to 3.2.2, but fixes a regression that - unfortunately crept into 3.2.2. The regression causes an assertion - failure in Valgrind when running certain obscure SSE code fragments - on x86-linux and amd64-linux. Please do not use (or package) 3.2.2; - instead use 3.2.3. - </p> +unfortunately crept into 3.2.2. The regression causes an assertion=20 +failure in Valgrind when running certain obscure SSE code fragments=20 +on x86-linux and amd64-linux. Please do not use (or package) 3.2.2;=20 +instead use 3.2.3.</p> =20 =20 -<h3>Release 3.2.2 (superseded by 3.2.3)</h3> +<div class=3D"hr_brown"><hr/></div> =20 -<p>valgrind 3.2.2 (tar.bz2)</a>=20 -[4016Kb] - 22 January 2007.<br /> -For {x86,amd64,ppc32,ppc64}-linux.<br /> -<span class=3D"md5sum">md5: de3f68da0c8b7fc72b8fded95a9aebbc</span></p> -<p>You may want to look at the=20 -<a href=3D"/docs/manual/dist.news.html">3.2.2 release notes</a>. -</p> +<h3>Valkyrie 1.2.0</h3> =20 -<p>3.2.2 builds and runs its regression tests on at least the following -platforms, and probably more:</p> +<p><a href=3D"/downloads/valkyrie-1.2.0.tar.bz2">valkyrie 1.2.0 (tar.bz2= )</a> +[370Kb] - June 7 2006.<br /> +<span class=3D"md5sum">md5: 231982dc7063593f15ed2f93b85d0b2e</span></p> =20 -<ul> - <li>x86: Red Hat 7.3, SuSE 10.0, 10.1, 10.2, Fedora Core 6</li> - <li>amd64: SuSE 10.2</li> - <li>ppc32: SuSE 10.1, SuSE 10.2, SLES8</li> - <li>ppc64: SuSE 10.1, SLES 8</li> -</ul> +<p><a href=3D"http://www.open-works.co.uk/projects/valkyrie.html">Valkyr= ie</a>=20 +is a GUI for valgrind 3.0.0 or higher, as that was the first valgrind re= lease to support XML output, which valkyrie requires. It also has an XML= merging tool for Memcheck outputs (vk_logmerge). This tarball is known = to build and work with valgrind-3.2.0.</p> =20 -<p>We believe it should work on Linux distributions with kernel 2.4 or -2.6 and glibc 2.2.X, 2.3.X, 2.4.X or 2.5.X. Note that the PowerPC ports -also work on POWER4 and POWER5 running Linux.</p> =20 - -<!-- -<h3>Release 3.2.1</h3> - -<p><a href=3D"/downloads/valgrind-3.2.1.tar.bz2">valgrind 3.2.1 (tar.bz2= )</a>=20 -[4052Kb] - 16 September 2006.<br /> -For {x86,amd64,ppc32,ppc64}-linux.<br /> -<span class=3D"md5sum">md5: 9407d33961186814cef0e6ecedfd6318</span></p> -<p>You may want to look at the=20 -<a href=3D"/docs/manual/dist.news.html">3.2.1 release notes</a>. -</p> - -<p>3.2.1 builds and runs its regression tests on at least the following -platforms, and probably more:</p> - -<ul> - <li>x86: Red Hat 7.3, SuSE 10.0, 10.1, 10.2alpha3.</li> - <li>amd64: SuSE 10.1</li> - <li>ppc32: SuSE 10.0, SuSE 10.1, SLES8.</li> - <li>ppc64: SuSE 10.1, SLES 8</li> -</ul> - -<p>We believe it should work on Linux distributions with kernel 2.4 or -2.6 and glibc 2.2.X, 2.3.X or 2.4.X. Note that the PowerPC ports -also work on POWER4 and POWER5 running Linux.</p> ---> - - -<!-- -<h3>Release 3.2.0</h3> - -<p><a href=3D"/downloads/valgrind-3.2.0.tar.bz2">valgrind 3.2.0 (tar.bz2= )</a>=20 -[4059Kb] - 7 June 2006.<br /> -For {x86,amd64,ppc32,ppc64}-linux.<br /> -<span class=3D"md5sum">md5: c418026ce7c38a740ef17efe59509fcf</span></p> -<p>You may want to look at the=20 -<a href=3D"/docs/manual/dist.news.html">3.2.0 release notes</a>. -</p> - -<p>3.2.0 builds and runs its regression tests on at least the following -platforms, and probably more:</p> - -<ul> - <li>x86: Red Hat 7.3, 8.0, Fedora Core 4, 5, SuSE 9.3, 10.0, 10.1</li> - <li>amd64: Fedora Core 2, 3, 5, SuSE 10.1</li> - <li>ppc32: Fedora Core 5, YDL 4.0, SLES 8, SuSE 10.0</li> - <li>ppc64: Fedora Core 5, YDL 4.0, SLES 8</li> -</ul> - -<p>We believe it should work on Linux distributions with kernel 2.4 or -2.6 and glibc 2.2.X, 2.3.X or 2.4.X. Note that the PowerPC ports -also work on POWER4 and POWER5 running Linux.</p> ---> - - -<p> -<a href=3D"/downloads/valkyrie-1.2.0.tar.bz2">valkyrie 1.2.0 (tar.bz2)</= a> -[370Kb] contains the -<a href=3D"http://www.open-works.co.uk/projects/valkyrie.html">Valkyrie<= /a> -GUI and XML merging tool for Memcheck outputs (vk_logmerge). -This tarball is known to build and work with 3.2.0.<br /> -<span class=3D"md5sum">md5: 231982dc7063593f15ed2f93b85d0b2e</span></p> -</p> - <div class=3D"hr_brown"><hr/></div> =20 <h3>RPMs / Binaries</h3> @@ -148,3 +67,6 @@ the Memcheck tool. Therefore, it's best to use Valgrind on the most capable machine you can get your hands on. </p> + + +</div> Modified: trunk/downloads/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/downloads/guis.html 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/downloads/guis.html 2007-02-01 11:36:45 UTC (rev 310) @@ -27,14 +27,13 @@ Estievenart.</p></li> =20 =20 -<li><p><a href=3D"http://www.open-works.co.uk/projects/valkyrie.html">Va= lkyrie</a>=20 +<li><p><a href=3D"http://www.open-works.net/projects/valkyrie.html">Valk= yrie</a>=20 is a Qt-based GUI for the Valgrind 3.X line. -You can download the latest -version (1.2.0, for use with Valgrind 3.0.0 and later) from -<a href=3D"/downloads/current.html">the Valgrind download page</a>. +You can download the latest version (1.2.0, for use with Valgrind 3.0.0=20 +and later) from the <a href=3D"/downloads/current.html">Valgrind downloa= d page</a>. 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> +the merged result in the GUI.</p></li> =20 =20 </ul> 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 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/downloads/old.html 2007-02-01 11:36:45 UTC (rev 310) @@ -13,6 +13,122 @@ =20 =20 <div class=3D"hr_brown"><hr/></div> +<h3>valgrind-3.2.2</h3> + +<p>valgrind 3.2.2 (tar.bz2)</a>=20 +[4016Kb] - 22 January 2007.<br /> +For {x86,amd64,ppc32,ppc64}-linux.<br /> +<span class=3D"md5sum">md5: de3f68da0c8b7fc72b8fded95a9aebbc</span></p> + +<p>3.2.2 builds and runs its regression tests on at least the following +platforms, and probably more:</p> + +<ul> + <li>x86: Red Hat 7.3, SuSE 10.0, 10.1, 10.2, Fedora Core 6</li> + <li>amd64: SuSE 10.2</li> + <li>ppc32: SuSE 10.1, SuSE 10.2, SLES8</li> + <li>ppc64: SuSE 10.1, SLES 8</li> +</ul> + +<p>We believe it should work on Linux distributions with kernel 2.4 or +2.6 and glibc 2.2.X, 2.3.X, 2.4.X or 2.5.X. Note that the PowerPC ports +also work on POWER4 and POWER5 running Linux.</p> + + + +<div class=3D"hr_brown"><hr/></div> +<h3>valgrind-3.2.1</h3> + +<p><a href=3D"/downloads/archive/valgrind-3.2.1.tar.bz2">valgrind 3.2.1 = (tar.bz2)</a>=20 +[4052Kb] - 16 September 2006.<br /> +For {x86,amd64,ppc32,ppc64}-linux.<br /> +<span class=3D"md5sum">md5: 9407d33961186814cef0e6ecedfd6318</span></p> + +<p>3.2.1 builds and runs its regression tests on at least the following +platforms, and probably more:</p> + +<ul> + <li>x86: Red Hat 7.3, SuSE 10.0, 10.1, 10.2alpha3.</li> + <li>amd64: SuSE 10.1</li> + <li>ppc32: SuSE 10.0, SuSE 10.1, SLES8.</li> + <li>ppc64: SuSE 10.1, SLES 8</li> +</ul> + +<p>We believe it should work on Linux distributions with kernel 2.4 or +2.6 and glibc 2.2.X, 2.3.X or 2.4.X. Note that the PowerPC ports +also work on POWER4 and POWER5 running Linux.</p> + + + +<div class=3D"hr_brown"><hr/></div> +<h3>valgrind-3.2.0</h3> + +<p><a href=3D"/downloads/archive/valgrind-3.2.0.tar.bz2">valgrind 3.2.0 = (tar.bz2)</a>=20 +[4059Kb] - 7 June 2006.<br /> +For {x86,amd64,ppc32,ppc64}-linux.<br /> +<span class=3D"md5sum">md5: c418026ce7c38a740ef17efe59509fcf</span></p> + +<p>3.2.0 builds and runs its regression tests on at least the following +platforms, and probably more:</p> + +<ul> + <li>x86: Red Hat 7.3, 8.0, Fedora Core 4, 5, SuSE 9.3, 10.0, 10.1</li> + <li>amd64: Fedora Core 2, 3, 5, SuSE 10.1</li> + <li>ppc32: Fedora Core 5, YDL 4.0, SLES 8, SuSE 10.0</li> + <li>ppc64: Fedora Core 5, YDL 4.0, SLES 8</li> +</ul> + +<p>We believe it should work on Linux distributions with kernel 2.4 or +2.6 and glibc 2.2.X, 2.3.X or 2.4.X. Note that the PowerPC ports +also work on POWER4 and POWER5 running Linux.</p> + + + +<div class=3D"hr_brown"><hr/></div> +<h3>valgrind-3.1.1</h3> + +<p><a href=3D"/downloads/valgrind-3.1.1.tar.bz2">valgrind 3.1.1 (tar.bz2= )</a> +[3074Kb] - 15 March 2006.<br /> +For {x86,amd64,ppc32}-linux.<br /> +<span class=3D"md5sum">md5: 3bbfafedb59c19bf75977381ce2eb6d7</span></p> + +<p>3.1.1 builds and runs its regression tests on at least the following +platforms, and probably more:</p> + +<ul> + <li>x86 running Red Hat 7.3, SuSE 10.0</li> + <li>amd64 running SuSE 9.2</li> + <li>ppc32 running SuSE 10, YDL4.0</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-3.1.0</h3> + +<p><a href=3D"/downloads/archive/valgrind-3.1.0.tar.bz2">valgrind 3.1.0 = (tar.bz2)</a>=20 +[3054Kb] - 25 November 2005.<br /> +For {x86,amd64,ppc32}-linux.<br /> +<span class=3D"md5sum">md5: d92156e9172dc6097e56c69ea9c88013</span></p> + +<p>3.1.0 builds and runs its regression tests on at least the following +platforms, and probably more:</p> + +<ul> + <li>x86 running Red Hat 7.3, SuSE 9.2, 9.3, 10.0, Fedora Core 4</li> + <li>amd64 running SuSE 9.2, Fedora Core 2, 3, 4</li> + <li>ppc32 running SuSE 10, FC5test1, YDL4.0</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-3.0.1</h3> =20 <p><a href=3D"/downloads/archive/valgrind-3.0.1.tar.bz2">valgrind 3.0.1 = (tar.bz2)</a>=20 @@ -30,7 +146,6 @@ <li>x86 running SuSE 9.1, 9.2, 9.3, Fedora Core 4</li> </ul> =20 - <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> =20 @@ -63,7 +178,7 @@ =20 =20 <div class=3D"hr_brown"><hr/></div> -<h3>Valgrind for PowerPC</h3> +<h3>valgrind-2.4.1 for PowerPC</h3> =20 <p>Paul Mackerras' PPC32/Linux port of Valgrind 2.4.1 is now available h= ere: <a href=3D"/downloads/pmk/valgrind-2.4.1-ppc.tar.bz2"> 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 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/downloads/repository.html 2007-02-01 11:36:45 UTC (rev 310) @@ -19,10 +19,13 @@ =20 =20 <div class=3D"hr_brown"><hr/></div> + <h2>The Current (3.0 and later) Repository</h2> =20 -<!--<p>If you want to browse the current repository you can use the -<a href=3D"http://svn.valgrind.org/">web interface</a>.</p>--> +<!-- +<p>If you want to browse the current repository you can use the +<a href=3D"http://svn.valgrind.org/">web interface</a>.</p> +--> =20 <p>To check out code from the current repository (anonymous, read-only S= VN access), do this:</p> @@ -31,11 +34,8 @@ svn co svn://svn.valgrind.org/valgrind/trunk valgrind </pre> =20 -<p>As of January 2006, the code from this repository works -well on x86/Linux, AMD64/Linux and PPC32/Linux. PPC64/Linux=20 -has received a lot of attention recently and support for it is -now at beta-release quality. -</p> +<p>As of January 2007, the code from this repository works +well on x86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux.</p> =20 <p> To build the checked out code, follow the instructions in the @@ -59,7 +59,8 @@ to have the svnversion program (part of the Subversion client suite) in = your path - if you don't, building the VEX library will fail.</p> =20 -<!-- +<?php +/* <p> If you are behind a firewall that doesn't allow the svn protocol, you can do an http checkout instead: @@ -72,11 +73,13 @@ Older versions of Subversion may not support the <code>--ignore-externals</code> flag. </p> ---> +*/ +?> =20 =20 =20 <div class=3D"hr_brown"><hr/></div> + <h2>The Old (2.4 and earlier) Repository</h2> =20 <p>If you want to browse the old repository you can use the=20 Modified: trunk/downloads/variants.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/variants.html 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/downloads/variants.html 2007-02-01 11:36:45 UTC (rev 310) @@ -83,14 +83,13 @@ =20 </dl> =20 -<p><b>Bryan Meredith</b> <brainmurders at googlemail com> has -written <a href=3D"http://www.brainmurders.demon.co.uk/omega.html"> -Omega</a>, an instant memory leak detector tool designed to give the -location that a leak occurs, as it occurs. -</p> +<p><b>Bryan Meredith</b>=20 +<brainmurder= 5;@googlemail.&#= 99;om>=20 +has written <a href=3D"http://www.brainmurders.demon.co.uk/omega.html">O= mega</a>,=20 +an instant memory leak detector tool designed to give the location that = a leak=20 +occurs, as it occurs.</p> =20 =20 - <?php break; =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 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/help/projects.html 2007-02-01 11:36:45 UTC (rev 310) @@ -21,27 +21,27 @@ addresses, how does it affect the code base's structure, and so on. Such is the nature of all free software projects. However, if you consistently submit high quality patches, you may be granted write -access to the repository. This is how most of the current developers got -involved with Valgrind.</p> +access to the repository. This is how most of the current developers=20 +got involved with Valgrind.</p> =20 =20 <h2>Documentation</h2> =20 <h3>Using Valgrind in an Automated Test Suite</h3> -<p>Various people have managed to set up an automated test suite that us= es -Memcheck, and automatically reports if Memcheck finds any errors. This -usually relies on the VALGRIND_COUNT_ERRORS client request, but it is no= t -totally straightforward. It would be great to have a section in the man= ual -that describes how to do this well. This would be best written by someo= ne -who has actually set up such a test suite.</p> +<p>Various people have managed to set up an automated test suite that=20 +uses Memcheck, and automatically reports if Memcheck finds any errors. =20 +This usually relies on the VALGRIND_COUNT_ERRORS client request, but it=20 +is not totally straightforward. It would be great to have a section in=20 +the manual that describes how to do this well. This would be best=20 +written by someone who has actually set up such a test suite.</p> =20 =20 <h2>Software Infrastructure</h2> =20 <h3>Improving the Performance Testing Suite</h3> -<p>We have a growing suite of performance benchmarks in the perf/ direct= ory, -which would benefit from more programs. We have a mix of two kinds of -programs:</p> +<p>We have a growing suite of performance benchmarks in the=20 +perf/ directory, which would benefit from more programs. We have a mix=20 +of two kinds of programs:</p> =20 <ol> <li><p>Real programs. Ones like the SPEC2000 benchmarks would be ideal, @@ -50,8 +50,8 @@ <li><p>Artificial programs that stress performance-critical subsystems. For example <a href=3D"http://bugs.kde.org/show_bug.cgi?id=3D105039">b= ug report #105039</a> has an example program that does many malloc and - free calls, and has many heap blocks live at one time. This exposed a - performance bug in Valgrind's heap allocator.</p></li> + free calls, and has many heap blocks live at one time. This exposed + a performance bug in Valgrind's heap allocator.</p></li> </ol> =20 The programs should be fairly small (preferably a few thousand lines at @@ -67,15 +67,16 @@ regressions. Equally useful would be an automated system for spotting performance regressions (or improvements).</p> =20 -<p>It would be nice to have scripts to run the performance benchmarks ev= ery -night. The nightly measurements should be kept and ideally there would = be a -system for producing graphs that show the performance changes over time. -You'd have to specify somehow where the previous measurements would be -stored, perhaps that would be a command line argument to the script.</p> +<p>It would be nice to have scripts to run the performance benchmarks=20 +every night. The nightly measurements should be kept and ideally there=20 +would be a system for producing graphs that show the performance changes= =20 +over time. You'd have to specify somehow where the previous measurements= =20 +would be stored, perhaps that would be a command line argument to the=20 +script.</p> =20 -<p>The scripts in nightly/ for doing the nightly regression tests would = be the -right place to start on this. (Added August 27, 2005; updated December= 15, -2005)</p> +<p>The scripts in nightly/ for doing the nightly regression tests would=20 +be the right place to start on this. (Added August 27, 2005; updated=20 +December 15, 2005)</p> =20 =20 <h3>Regression test brittleness</h3> @@ -87,11 +88,11 @@ about 10 or 15 failures that should not happen due to these differences.</p> =20 -<p>Improving things will require either additional expected output files= (the -*.stderr.exp* and *.stdout.exp* files in the tests/ directories), or mor= e -clever output filters (the filters have names like filter_stderr). If y= ou -attempt to improve the filters, you should be careful not to remove so m= uch -information that the test becomes weaker. (Added August 27, 2005)</p> +<p>Improving things will require either additional expected output files= =20 +(the *.stderr.exp* and *.stdout.exp* files in the tests/ directories), o= r=20 +more clever output filters (the filters have names like filter_stderr). = =20 +If you attempt to improve the filters, you should be careful not to remo= ve=20 +so much information that the test becomes weaker. (Added August 27, 200= 5)</p> =20 =20 <h3>Regression test gaps</h3> @@ -108,37 +109,37 @@ be useful.</p></li> </ul> =20 -<p>Fixing these gaps is not very hard, just tedious. (Added August 27, -2005; updated November 15, 2005)</p> +<p>Fixing these gaps is not very hard, just tedious. (Added August 27, = 2005; +updated November 15, 2005)</p> =20 <h3>Unit regression tests</h3> -<p>The regression tests are good system-level tests, but we have almost = no unit -testing, which is bad. We would like to pull out individual Valgrind -modules into test harnesses. These can then be tested like normal progr= ams, -using normal testing tools, such as gcov (for test coverage) and Valgrin= d -itself.</p> +<p>The regression tests are good system-level tests, but we have almost=20 +no unit testing, which is bad. We would like to pull out individual=20 +Valgrind modules into test harnesses. These can then be tested like nor= mal=20 +programs, using normal testing tools, such as gcov (for test coverage) a= nd=20 +Valgrind itself.</p> =20 -<p>The test memcheck/tests/oset_test.c is one unit test we have. It tes= ts the -m_oset module. It uses some preprocessing hacks to replace calls to -Valgrind-internal functions with calls to the standard versions, eg. cal= ling -printf() instead of VG_(printf)(). memcheck/tests/vgtest_ume.c is anoth= er -one, although it has some oddities that make it not such a good -example.</p> +<p>The test memcheck/tests/oset_test.c is one unit test we have. It=20 +tests the <tt>m_oset module</tt>. It uses some preprocessing hacks to=20 +replace calls to Valgrind-internal functions with calls to the standard=20 +versions, eg. calling <tt>printf()</tt> instead of <tt>VG_(printf)()</tt= >.=20 +<tt>memcheck/tests/vgtest_ume.c</tt> is another one, although it has som= e=20 +oddities that make it not such a good example.</p> =20 <p>(Note that when this test runs, the Valgrind built in the tree is act= ually running and testing part of its own code! Which is quirky but fine in practice.)</p> =20 -<p>Some modules will be more amenable to this approach than others; the = fewer -other modules a module depends on, the easier it is. m_oset is a case i= n -point, as it only imports 5 pub_core_* header files. Other files in -coregrind/ that would be good candidates include:</p> +<p>Some modules will be more amenable to this approach than others; the=20 +fewer other modules a module depends on, the easier it is. m_oset is a=20 +case in point, as it only imports 5 pub_core_* header files. Other file= s=20 +in coregrind/ that would be good candidates include:</p> =20 <ul> <li>m_debuglog.c</li> <li>m_execontext.c</li> -<li>m_hashtable.c (the test would be very similar to - m_oset.c's),</li> +<li>m_hashtable.c (the test would be very similar to=20 + <tt>m_oset.c</tt>'s),</li> <li>m_libc{assert,base,file,mman,print,proc,signal}.c</li> <li>m_mallocfree.c (a test for this would be particularly helpful)</li> 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 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/index.html 2007-02-01 11:36:45 UTC (rev 310) @@ -12,7 +12,7 @@ <p> </p> =20 <p>Valgrind is an=20 -<a href=3D"http://www.valgrind.org/gallery/awards.html">award-winning</a= >=20 +<a href=3D"/gallery/awards.html">award-winning</a>=20 suite of tools for debugging and profiling Linux programs. With the tools that come with Valgrind, you can automatically detect many memory management and threading bugs, @@ -38,7 +38,7 @@ <h2 align=3D"center">Recent News</h2> =20 <ul> - <li><p>January 29 2007: valgrind-3.2.3, + <li><p><?php echo $config['release-date'].": ".$config['release-version= ']; ?>, for x86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux, is available.=20 (<a href=3D"/docs/manual/dist.news.html">release notes</a>). 3.2.3 is almost identical to 3.2.2, but fixes a regression that=20 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 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/info/developers.html 2007-02-01 11:36:45 UTC (rev 310) @@ -18,7 +18,7 @@ </td></tr> =20 <tr valign=3D"top"> - <td><b>Cerion Armour-Brown</b><br /> + <td><b>Cerion Armour-Brown</b><br /> <?php echo vgemail('cerion'); ?></td> <td>Cerion has been working on PowerPC instruction set support using the Vex dynamic-translation framework.</td> 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 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/info/news.html 2007-02-01 11:36:45 UTC (rev 310) @@ -69,7 +69,7 @@ <li><p>August 1 2005: A new stable version, 2.4.1, is available.</p></li> =20 - <li><p>March 24, 2005:<br /> A new stable release,=20 + <li><p>March 24, 2005: A new stable release,=20 <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, @@ -84,38 +84,38 @@ list will receive announcements of new Valgrind releases. </p></li> =20 - <li><p>August 31, 2004:<br /> A new stable release,=20 - <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> + <li><p>August 31, 2004: A new stable release,=20 + <a href=3D"/downloads/old.html">valgrind 2.2.0</a>, is available.=20 + 2.2.0 brings many improvements over 2.0.0, and includes the new=20 + Massif heap-profiling tool.</p></li> =20 - <li>July 18 2004:<br /> A new developer release,=20 + <li>July 18 2004: A new developer release,=20 <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 + <li>March 12 2004: A new developer release,=20 <a href=3D"/downloads/old.html">valgrind 2.1.1</a>,=20 is available.</li> =20 - <li>March 04 2004:<br /> An experimental PowerPC port + <li>March 04 2004: An experimental PowerPC port is available.</li> =20 - <li>February 15 2004:<br /> Valgrind CVS now includes=20 + <li>February 15 2004: Valgrind CVS now includes=20 <a href=3D"/info/tools.html#massif">Massif</a>, a heap profiling tool.</li> =20 - <li>January 27 2004:<br /> We have a new page listing=20 + <li>January 27 2004: We have a new page listing=20 <a href=3D"/gallery/users.html">projects using Valgrind</a>.</li> =20 - <li>January 15 2004:<br /> Valgrind awarded a merit (bronze)=20 + <li>January 15 2004: Valgrind awarded a merit (bronze)=20 <a href=3D"http://opensource.org/OSA/awards.php">Open Source Award</a>=20 (<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 + <li>December 14 2003: A new developer release,=20 <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 + <li>November 11 2003: A new stable release,=20 <a href=3D"/downloads/old.html">valgrind 2.0.0</a>,=20 is available.</li> =20 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 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/info/platforms.html 2007-02-01 11:36:45 UTC (rev 310) @@ -1,21 +1,24 @@ <h1>Supported Platforms</h1> =20 +<!-- <p>We are working to make future Valgrinds (3.0.0 and above) more portable.</p> =20 <div class=3D"hr_brown"><hr/></div> - +--> +<br/> <a name=3D"curr_mainline"></a><h2>Current Mainline</h2> =20 -<p>The Valgrind 3.0.X series supports the following platforms.</p> +<p>The Valgrind 3.2.X series supports the following platforms.</p> <ul> <li><b>x86/Linux:</b> support is mature and almost complete.</li> -<li><b>AMD64/Linux:</b> support is new but fairly complete.</li> -<li><b>PPC32/Linux:</b> support is new, incomplete, but improving.</li> +<li><b>AMD64/Linux:</b> support is mature and almost complete.</li> +<li><b>PPC32/Linux:</b> support is new but fairly complete.</li> +<li><b>PPC64/Linux:</b> support is new but fairly complete.</li> </ul> =20 <p>You must be running Linux kernel 2.4.X, 2.5.X or 2.6.X, and glibc 2.2= .X, -2.3.X or 2.4.X. That covers the vast majority of installed systems at +2.3.X, 2.4.X or 2.5.X. That covers the vast majority of installed system= s at present.</p> =20 <p>For details of which distributions the current release @@ -41,12 +44,6 @@ <a href=3D"http://www.freebsd.org/cgi/ports.cgi?query=3Dvalgrind">th= is FreeBSD page</a>.</p></li> =20 -<li><p><b>PPC32/Linux:</b> Paul Mackerras has an experimental port of - Valgrind 2.X which you can - <a href=3D"/downloads/variants.html?pmk">download here</a>.=20 - This was the basis of the PPC32/Linux port included in Valgrind 3.0.= 0 - and above.</p></li> - <li><p><b>x86/NetBSD:</b> Eric Auge, Kailash Sethuraman and Peter Bex are doing a port of Valgrind 3.X, available at=20 <a href=3D"http://vg4nbsd.berlios.de/">this page</a>.=20 @@ -112,6 +109,6 @@ As ever we retain a flexible approach, and are interested in hearing=20 your comments/porting needs if you have any.</p> =20 -<p>March 31, 2006.</p> +<p>February 1, 2007.</p> =20 =20 Modified: trunk/php/.htconfx =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/.htconfx 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/php/.htconfx 2007-02-01 11:36:45 UTC (rev 310) @@ -6,17 +6,17 @@ $included_config =3D true; =20 /*------ change these lines to suit your environment ------*/ -/* --- This is for phoenix --- */ +/* --- This is for phoenix --- $base_url =3D "http://valgrind.local"; -$base_dir =3D "/home/de/WebPages/valgrind-www/trunk"; +$base_dir =3D "/home/de/WebSites/valgrind-www/trunk"; +*/ =20 - -/* --- This is for Exonetric --=20 +/* --- This is for Exonetric -- */ $base_url =3D "http://www.valgrind.org"; $base_dir =3D "/usr/local/www/sites/valgrind-www"; -*/ =20 =20 + /*---------------------------------------------------------*/ $config =3D array ( 'base_url' =3D> $base_url, @@ -24,7 +24,7 @@ 'inc_dir' =3D> $base_dir . '/php/', 'img_dir' =3D> $base_dir . '/images/', =20 - 'dt_copyright' =3D> '2000-2007 ', + 'dt_copyright' =3D> '2000-2007', =20 /* current release info */ 'release-date' =3D> 'January 29 2007', Modified: trunk/php/funcs.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/funcs.php 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/php/funcs.php 2007-02-01 11:36:45 UTC (rev 310) @@ -60,13 +60,13 @@ } =20 /* return the result */ - return '<a href=3D"mailto:' .$addr. '">' = .$link_txt. "</a>"; + return '<a href=3D"mailto:' .$addr. '= ">' .$link_txt. "</a>"; } =20 =20 - /* used by /gallery/survey-xx/ pages */ -function chunkNav( $prev, $top, $next ) { +function chunkNav( $prev, $top, $next ) +{ $prev =3D ( $prev =3D=3D '' ) ? ' ' : '<< '.$prev; $next =3D ( $next =3D=3D '' ) ? ' ' : $next. ' >>'; return ' Modified: trunk/php/header.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/header.php 2007-01-30 04:40:37 UTC (rev 309) +++ trunk/php/header.php 2007-02-01 11:36:45 UTC (rev 310) @@ -13,14 +13,13 @@ <html xmlns=3D"http://www.w3.org/1999/xhtml" xml:lang=3D"en" lang=3D"en"= > <head> <title><?php echo $curr_page['title']; ?></title> - <meta http-equiv=3D"Content-Type"=20 - content=3D"text/html; charset=3Diso-8859-1" /> + <meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8= 859-1" /> <meta http-equiv=3D"Content-Style-Type" content=3D"text/css"/> <style type=3D"text/css">@import url('/css/valgrind.css');</style> <link rel=3D"shortcut icon" href=3D"/favicon.ico" /> <link rel=3D"icon" href=3D"/favicon.ico" type=3D"image/x-icon" /> - <meta name=3D"description" content=3D"Official Home Page for valgrind, = a suite of tools for debugging and profiling. Automatically detect memory= management and threading bugs, and perform detailed profiling. The curr= ent stable version is valgrind 3.0.0."/> - <meta name=3D"keywords" content=3D"Valgrind Memcheck Addrcheck Cachegri= nd Massif Helgrind memory-management uninitialised memory memory leaks pa= ssing uninitialised memory overlapping pointers misuses of the POSIX pthr= eads"/> + <meta name=3D"description" content=3D"Official Home Page for valgrind, = a suite of tools for debugging and profiling. Automatically detect memory= management and threading bugs, and perform detailed profiling. The curr= ent stable version is <?php echo $config['release-version']; ?>."/> + <meta name=3D"keywords" content=3D"Valgrind Memcheck Cachegrind Callgri= nd Massif Helgrind memory-management uninitialised memory memory leaks pa= ssing uninitialised memory overlapping pointers misuses of the POSIX pthr= eads"/> </head> =20 <!-- dont we all just wish IE && Netscape 4.x to /dev/null --> |
|
From: Tom H. <to...@co...> - 2007-02-01 09:02:18
|
In message <341...@ma...>
Kumar Rangarajan <kum...@gm...> wrote:
> I also should add that my company is working with a recent request on
> this mailing list about moving Valgrind to Solaris/x86. Hopefully
> that will come thro and we could contribute that back to OS. Any
> pointers here would certainly help (estimation, documents, etc)
I take it you're aware that there has been previous work on porting
to solaris-x86 and solaris-amd64 at different times.
If you search the archives for the developer list you should find some
details of the people that were involved and how far they got.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|
|
From: Kailash S. <hs...@gm...> - 2007-02-01 08:49:03
|
Hi Ivan, I do know that there is a working port of valgrind 2.4 to FreeBSD at http://www.rabson.org/ I believe its packaged in freebsd's ports as well. I am doing a NetBSD port which is based on -current ( we merge on occasions but as those are very time consuming, we have not in a while) unfortunately is suffering from a lack of free time (juggling a day job that is demanding). I would not mind more help on that aspect. Currently it runs, and we are in the process of trying to pass all relevant regression tests before making any formal release about it. Also, the NetBSD port addresses most common issues which *BSD derivatives will face when porting valgrind, such as signal handling, passing parameters by stack to syscalls, changes to the code which loads the client etc. If there is a concerted and open effort to port valgrind to any other *BSD architecture, I would love to share and abstract these fixes, but currently they reside in our tree at http://vg4nbsd.berlios.de . Of course in an ideal world, time would not be a constraint and a decent port will materialise soon and hopefully integrated into the main line. Regards, Kailash On 2/1/07, Ivan Novick <iv...@0x...> wrote: > Hi, > > Does anyone know if there has been much progress on getting Valgrind working > on Free-BSD? > > Thanks, > Ivan > > -- > Ivan Novick > iv...@0x... > http://www.0x4849.net > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job > easier. > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > > _______________________________________________ > Valgrind-developers mailing list > Val...@li... > https://lists.sourceforge.net/lists/listinfo/valgrind-developers > > > |
|
From: <js...@ac...> - 2007-02-01 08:21:58
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2007-02-01 09:00:01 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 219 tests, 10 stderr failures, 6 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/ppc32/jm-fp (stdout) none/tests/ppc32/jm-fp (stderr) none/tests/ppc32/round (stdout) none/tests/ppc32/round (stderr) none/tests/ppc32/test_fx (stdout) none/tests/ppc32/test_fx (stderr) none/tests/ppc32/test_gx (stdout) |
|
From: Ivan N. <iv...@0x...> - 2007-02-01 07:51:12
|
Hi, Does anyone know if there has been much progress on getting Valgrind working on Free-BSD? Thanks, Ivan -- Ivan Novick iv...@0x... http://www.0x4849.net |
|
From: <js...@ac...> - 2007-02-01 05:31:42
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2007-02-01 04:55:01 GMT Checking out vex source tree ... done Building vex ... done Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 254 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Kumar R. <kum...@gm...> - 2007-02-01 04:42:15
|
Hi Folks, I recently signed up to this mailing list. I have been watching the activity in this list for a while, and thought it was maybe appropriate to introduce myself first. I am Kumar Rangarajan, and I am from India, and interested in program analysis tools. My experience for the last 6-7 years has been developing/enhancing a very similar tool, Purify! Before that I was with the HPUX compiler team, working on the linker/loader. I was always piqued by Valgrind when I was in Rational/IBM, but couldnt look at it, as it would have obviously violated a thousand rules :-) I have since moved on from IBM and so one of the first things I did was to signup to the Valgrind developer mailing list. I am interested to contribute to Valgrind. I could start off with running your test suites. My company has a bunch of hetrogenous systems (linux/HPUX/Solaris/IA64), which I could probably leverage. I also have a personal Mac(x86), which I could use. I also should add that my company is working with a recent request on this mailing list about moving Valgrind to Solaris/x86. Hopefully that will come thro and we could contribute that back to OS. Any pointers here would certainly help (estimation, documents, etc) Please do let me know if there is anything I can help with. Thanks, :-) - The problem with winning the rat race is that, even if u win, u r still a rat! |
|
From: Tom H. <th...@cy...> - 2007-02-01 03:23:26
|
Nightly build on dellow ( x86_64, Fedora Core 6 ) started at 2007-02-01 03:10:04 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 288 tests, 4 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) none/tests/pth_detached (stdout) |
|
From: Tom H. <th...@cy...> - 2007-02-01 03:22:47
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2007-02-01 03:15:02 GMT Results differ from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccjkmE7z.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccjkmE7z.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccjkmE7z.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccjkmE7z.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccjkmE7z.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccjkmE7z.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccjkmE7z.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccjkmE7z.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 rm insn_mmx.c insn_sse2.c insn_fpu.c insn_mmxext.c insn_sse.c insn_sse3.c insn_cmov.c insn_basic.c make[5]: Leaving directory `/tmp/valgrind.22807/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.22807/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.22807/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.22807/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.22807/valgrind' make: *** [check] Error 2 ================================================= == Results from 24 hours ago == ================================================= Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Last 20 lines of verbose log follow echo /tmp/ccTZMhMK.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccTZMhMK.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccTZMhMK.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccTZMhMK.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccTZMhMK.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccTZMhMK.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccTZMhMK.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' /tmp/ccTZMhMK.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 rm insn_mmx.c insn_sse2.c insn_fpu.c insn_mmxext.c insn_sse.c insn_sse3.c insn_cmov.c insn_basic.c make[5]: Leaving directory `/tmp/valgrind.22807/valgrind/none/tests/x86' make[4]: *** [check-am] Error 2 make[4]: Leaving directory `/tmp/valgrind.22807/valgrind/none/tests/x86' make[3]: *** [check-recursive] Error 1 make[3]: Leaving directory `/tmp/valgrind.22807/valgrind/none/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/tmp/valgrind.22807/valgrind/none' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/tmp/valgrind.22807/valgrind' make: *** [check] Error 2 ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Thu Feb 1 03:18:55 2007 --- new.short Thu Feb 1 03:22:41 2007 *************** *** 7,16 **** Last 20 lines of verbose log follow echo ! /tmp/ccTZMhMK.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccTZMhMK.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccTZMhMK.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccTZMhMK.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccTZMhMK.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccTZMhMK.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccTZMhMK.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccTZMhMK.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 --- 7,16 ---- Last 20 lines of verbose log follow echo ! /tmp/ccjkmE7z.s:4393: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccjkmE7z.s:4513: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccjkmE7z.s:4633: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccjkmE7z.s:4753: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccjkmE7z.s:4873: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccjkmE7z.s:4993: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccjkmE7z.s:5113: Error: no such instruction: `fisttpq -56(%ebp)' ! /tmp/ccjkmE7z.s:5233: Error: no such instruction: `fisttpq -56(%ebp)' make[5]: *** [insn_sse3.o] Error 1 |
|
From: Mukesh K. S. <sr...@ya...> - 2007-02-01 03:22:28
|
Hi All. I am looking to implement Valgrind and it's associated tools for mx21/mx27 flavour of architecture. Could I have some clue to start with. BR Mukesh K Srivastava --------------------------------- Need Mail bonding? Go to the Yahoo! Mail Q&A for great tips from Yahoo! Answers users. |
|
From: Tom H. <th...@cy...> - 2007-02-01 03:16:47
|
Nightly build on lloyd ( x86_64, Fedora Core 3 ) started at 2007-02-01 03:05:04 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 288 tests, 5 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/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: Tom H. <th...@cy...> - 2007-02-01 03:14:41
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2007-02-01 03:00:02 GMT Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 290 tests, 6 stderr failures, 1 stdout failure, 0 posttest failures == memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |
|
From: <js...@ac...> - 2007-02-01 01:16:17
|
Nightly build on g5 ( SuSE 10.1, ppc970 ) started at 2007-02-01 02:00:01 CET Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 225 tests, 6 stderr failures, 2 stdout failures, 0 posttest failures == memcheck/tests/deep_templates (stdout) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) none/tests/faultstatus (stderr) none/tests/fdleak_cmsg (stderr) none/tests/mremap (stderr) none/tests/mremap2 (stdout) |