You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
(122) |
Nov
(152) |
Dec
(69) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(6) |
Feb
(25) |
Mar
(73) |
Apr
(82) |
May
(24) |
Jun
(25) |
Jul
(10) |
Aug
(11) |
Sep
(10) |
Oct
(54) |
Nov
(203) |
Dec
(182) |
| 2004 |
Jan
(307) |
Feb
(305) |
Mar
(430) |
Apr
(312) |
May
(187) |
Jun
(342) |
Jul
(487) |
Aug
(637) |
Sep
(336) |
Oct
(373) |
Nov
(441) |
Dec
(210) |
| 2005 |
Jan
(385) |
Feb
(480) |
Mar
(636) |
Apr
(544) |
May
(679) |
Jun
(625) |
Jul
(810) |
Aug
(838) |
Sep
(634) |
Oct
(521) |
Nov
(965) |
Dec
(543) |
| 2006 |
Jan
(494) |
Feb
(431) |
Mar
(546) |
Apr
(411) |
May
(406) |
Jun
(322) |
Jul
(256) |
Aug
(401) |
Sep
(345) |
Oct
(542) |
Nov
(308) |
Dec
(481) |
| 2007 |
Jan
(427) |
Feb
(326) |
Mar
(367) |
Apr
(255) |
May
(244) |
Jun
(204) |
Jul
(223) |
Aug
(231) |
Sep
(354) |
Oct
(374) |
Nov
(497) |
Dec
(362) |
| 2008 |
Jan
(322) |
Feb
(482) |
Mar
(658) |
Apr
(422) |
May
(476) |
Jun
(396) |
Jul
(455) |
Aug
(267) |
Sep
(280) |
Oct
(253) |
Nov
(232) |
Dec
(304) |
| 2009 |
Jan
(486) |
Feb
(470) |
Mar
(458) |
Apr
(423) |
May
(696) |
Jun
(461) |
Jul
(551) |
Aug
(575) |
Sep
(134) |
Oct
(110) |
Nov
(157) |
Dec
(102) |
| 2010 |
Jan
(226) |
Feb
(86) |
Mar
(147) |
Apr
(117) |
May
(107) |
Jun
(203) |
Jul
(193) |
Aug
(238) |
Sep
(300) |
Oct
(246) |
Nov
(23) |
Dec
(75) |
| 2011 |
Jan
(133) |
Feb
(195) |
Mar
(315) |
Apr
(200) |
May
(267) |
Jun
(293) |
Jul
(353) |
Aug
(237) |
Sep
(278) |
Oct
(611) |
Nov
(274) |
Dec
(260) |
| 2012 |
Jan
(303) |
Feb
(391) |
Mar
(417) |
Apr
(441) |
May
(488) |
Jun
(655) |
Jul
(590) |
Aug
(610) |
Sep
(526) |
Oct
(478) |
Nov
(359) |
Dec
(372) |
| 2013 |
Jan
(467) |
Feb
(226) |
Mar
(391) |
Apr
(281) |
May
(299) |
Jun
(252) |
Jul
(311) |
Aug
(352) |
Sep
(481) |
Oct
(571) |
Nov
(222) |
Dec
(231) |
| 2014 |
Jan
(185) |
Feb
(329) |
Mar
(245) |
Apr
(238) |
May
(281) |
Jun
(399) |
Jul
(382) |
Aug
(500) |
Sep
(579) |
Oct
(435) |
Nov
(487) |
Dec
(256) |
| 2015 |
Jan
(338) |
Feb
(357) |
Mar
(330) |
Apr
(294) |
May
(191) |
Jun
(108) |
Jul
(142) |
Aug
(261) |
Sep
(190) |
Oct
(54) |
Nov
(83) |
Dec
(22) |
| 2016 |
Jan
(49) |
Feb
(89) |
Mar
(33) |
Apr
(50) |
May
(27) |
Jun
(34) |
Jul
(53) |
Aug
(53) |
Sep
(98) |
Oct
(206) |
Nov
(93) |
Dec
(53) |
| 2017 |
Jan
(65) |
Feb
(82) |
Mar
(102) |
Apr
(86) |
May
(187) |
Jun
(67) |
Jul
(23) |
Aug
(93) |
Sep
(65) |
Oct
(45) |
Nov
(35) |
Dec
(17) |
| 2018 |
Jan
(26) |
Feb
(35) |
Mar
(38) |
Apr
(32) |
May
(8) |
Jun
(43) |
Jul
(27) |
Aug
(30) |
Sep
(43) |
Oct
(42) |
Nov
(38) |
Dec
(67) |
| 2019 |
Jan
(32) |
Feb
(37) |
Mar
(53) |
Apr
(64) |
May
(49) |
Jun
(18) |
Jul
(14) |
Aug
(53) |
Sep
(25) |
Oct
(30) |
Nov
(49) |
Dec
(31) |
| 2020 |
Jan
(87) |
Feb
(45) |
Mar
(37) |
Apr
(51) |
May
(99) |
Jun
(36) |
Jul
(11) |
Aug
(14) |
Sep
(20) |
Oct
(24) |
Nov
(40) |
Dec
(23) |
| 2021 |
Jan
(14) |
Feb
(53) |
Mar
(85) |
Apr
(15) |
May
(19) |
Jun
(3) |
Jul
(14) |
Aug
(1) |
Sep
(57) |
Oct
(73) |
Nov
(56) |
Dec
(22) |
| 2022 |
Jan
(3) |
Feb
(22) |
Mar
(6) |
Apr
(55) |
May
(46) |
Jun
(39) |
Jul
(15) |
Aug
(9) |
Sep
(11) |
Oct
(34) |
Nov
(20) |
Dec
(36) |
| 2023 |
Jan
(79) |
Feb
(41) |
Mar
(99) |
Apr
(169) |
May
(48) |
Jun
(16) |
Jul
(16) |
Aug
(57) |
Sep
(32) |
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
|
|
|
|
|
|
1
(7) |
|
2
(8) |
3
(8) |
4
(7) |
5
(9) |
6
(9) |
7
(7) |
8
(7) |
|
9
(7) |
10
(6) |
11
(6) |
12
(8) |
13
(10) |
14
(14) |
15
(7) |
|
16
(7) |
17
(8) |
18
(7) |
19
(6) |
20
(8) |
21
(7) |
22
(7) |
|
23
(7) |
24
(12) |
25
(7) |
26
(7) |
27
(16) |
28
(12) |
29
(7) |
|
30
(10) |
31
(8) |
|
|
|
|
|
|
From: <js...@ac...> - 2006-07-14 13:14:28
|
Nightly build on minnie ( SuSE 10.0, ppc32 ) started at 2006-07-19 09:00:02 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 206 tests, 11 stderr failures, 5 stdout failures, 0 posttest failures == memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/leakotron (stdout) memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigaltstack (stderr) memcheck/tests/xml1 (stderr) none/tests/faultstatus (stderr) none/tests/mremap (stderr) 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: <sv...@va...> - 2006-07-14 06:17:47
|
Author: njn Date: 2006-07-14 07:17:44 +0100 (Fri, 14 Jul 2006) New Revision: 5984 Log: update Modified: trunk/docs/internals/release-HOWTO.txt Modified: trunk/docs/internals/release-HOWTO.txt =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/internals/release-HOWTO.txt 2006-07-08 08:29:20 UTC (rev 5= 983) +++ trunk/docs/internals/release-HOWTO.txt 2006-07-14 06:17:44 UTC (rev 5= 984) @@ -151,9 +151,9 @@ - Update the docs -- both the tarball'd docs, and the online-readable = docs. - Update www.valgrind.org/downloads/current.html. =20 - Update www.valgrind.org/downloads/old.html. =20 - - Put the release notes at www.valgrind.org/info/release-notes-X.Y.Z.t= xt. - Add a news item to the front page and also to valgrind.org/info/news= .html. - Include a link to the release notes. + Include a link to the release notes. Possibly remove any old releas= e + notices form the front page. - Update the "release-date" and "release-version" in php/.htconfx. - Other pages that might need updating: downloads/repository.html. =20 |
|
From: <sv...@va...> - 2006-07-14 06:02:21
|
Author: njn
Date: 2006-07-14 07:02:17 +0100 (Fri, 14 Jul 2006)
New Revision: 286
Log:
Add a couple of missing items to the news page. Hardwire in the current
release date and number in the news on the front page, since it will be
copied to the news page eventually where it must not change.
Modified:
trunk/index.html
trunk/info/news.html
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 2006-07-14 05:48:14 UTC (rev 285)
+++ trunk/index.html 2006-07-14 06:02:17 UTC (rev 286)
@@ -38,16 +38,16 @@
<h2 align=3D"center">Recent News</h2>
=20
<ul>
- <li><p><?php echo $config['release-date'].": ".$config['release-versio=
n']; ?>,
- for X86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux, is available.=
=20
- (<a href=3D"/docs/manual/dist.news.html">release notes</a>).</p></li>
+ <li><p>Jun 7 2006: valgrind-3.2.0,
+ for x86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux, is available.=20
+ (<a href=3D"/docs/manual/dist.news.html">release notes</a>).</p></li>
=20
- <li><p>November 21 2005: The results of the September survey have been
- put on the <a href=3D"/gallery/surveys.html">surveys page</a>.</p></li=
>
+ <li><p>November 21 2005: The results of the September survey have been
+ put on the <a href=3D"/gallery/surveys.html">surveys page</a>.</p></li>
=20
- <li><p>March 12 2005: A new mailing list,
- <?php echo vglink( 'vgannounce'); ?>, has been created. This low-volu=
me
- list will receive announcements of new Valgrind releases.</p></li>
+ <li><p>March 12 2005: A new mailing list,
+ <?php echo vglink( 'vgannounce'); ?>, has been created. This low-volum=
e
+ list will receive announcements of new Valgrind releases.</p></li>
</ul>
<br />
=20
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 2006-07-14 05:48:14 UTC (rev 285)
+++ trunk/info/news.html 2006-07-14 06:02:17 UTC (rev 286)
@@ -7,7 +7,14 @@
<p>Below are a few of the important events in the history of Valgrind:</=
p>
=20
<ul>
+ <li><p>Jun 7 2006: valgrind-3.2.0,
+ for x86/Linux, AMD64/Linux, PPC32/Linux and PPC64/Linux, is available.=20
+ (<a href=3D"/docs/manual/dist.news.html">release notes</a>).</p></li>
=20
+ <li><p>March 15 2006: A bug-fix release, 3.1.1, is available
+ (<a href=3D"/docs/manual/dist.news.html">release notes</a>).
+ We recommend upgrading from 3.1.0 to 3.1.1.</p></li>
+
<li><p>November 25 2005: Valgrind 3.1.0 is available=20
(<a href=3D"/docs/manual/dist.news.html">release notes</a>). This rele=
ase=20
runs on {x86,amd64,ppc32}-linux. 3.1.0 brings much improved support=20
|
|
From: <sv...@va...> - 2006-07-14 05:48:16
|
Author: njn Date: 2006-07-14 06:48:14 +0100 (Fri, 14 Jul 2006) New Revision: 285 Log: clarify Modified: trunk/info/tools.html Modified: trunk/info/tools.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/tools.html 2006-07-14 05:47:20 UTC (rev 284) +++ trunk/info/tools.html 2006-07-14 05:48:14 UTC (rev 285) @@ -69,8 +69,8 @@ callgraphs. It was folded into the main Valgrind distribution in=20 version 3.2.0. Available separately is an amazing visualisation tool,=20 <a href=3D"http://kcachegrind.sourceforge.net/cgi-bin/show.cgi/KcacheGri= ndIndex">KCachegrind</a>,=20 -which gives a much better overview of the data it collects; it can -also be used to visualise Cachegrind's output.</p> +which gives a much better overview of the data that Callgrind collects; +it can also be used to visualise Cachegrind's output.</p> =20 =20 <a name=3D"massif"></a> |
|
From: <sv...@va...> - 2006-07-14 05:47:26
|
Author: njn Date: 2006-07-14 06:47:20 +0100 (Fri, 14 Jul 2006) New Revision: 284 Log: Update Callgrind info. Modified: trunk/info/tools.html Modified: trunk/info/tools.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/tools.html 2006-07-03 01:43:58 UTC (rev 283) +++ trunk/info/tools.html 2006-07-14 05:47:20 UTC (rev 284) @@ -8,6 +8,7 @@ <li> </li> <li><a href=3D"#memcheck">Memcheck</a></li> <li><a href=3D"#cachegrind">Cachegrind</a></li> + <li><a href=3D"#callgrind">Callgrind</a></li> <li><a href=3D"#massif">Massif</a></li> <li><a href=3D"#helgrind">Helgrind</a></li> <li><a href=3D"#others">Other Tools</a></li> @@ -59,7 +60,19 @@ useful with programs written in any language. Cachegrind runs programs about 20--100x slower than normal.</p> =20 +<a name=3D"callgrind"></a> +<h3>Callgrind</h3> =20 +Callgrind, by Josef Weidendorfer, is an extension to=20 +<a href=3D"#cachegrind">Cachegrind</a>. It provides all the +information that Cachegrind does, plus extra information about +callgraphs. It was folded into the main Valgrind distribution in=20 +version 3.2.0. Available separately is an amazing visualisation tool,=20 +<a href=3D"http://kcachegrind.sourceforge.net/cgi-bin/show.cgi/KcacheGri= ndIndex">KCachegrind</a>,=20 +which gives a much better overview of the data it collects; it can +also be used to visualise Cachegrind's output.</p> + + <a name=3D"massif"></a> <h3>Massif</h3> =20 @@ -98,13 +111,6 @@ <a name=3D"others"></a> <h3>Other Tools</h3> =20 -<p><a href=3D"http://kcachegrind.sourceforge.net/cgi-bin/show.cgi/Kcache= GrindIndex">Callgrind</a>,=20 -by Josef Weidendorfer, is an extension to=20 -<a href=3D"#cachegrind">Cachegrind</a>. It provides all the -information that Cachegrind does, plus extra information about -callgraphs. It comes with an amazing visualisation tool, KCachegrind, wh= ich -gives a much better overview of the data it collects.</p> - <p>Several other Valgrind tools have been created: you can find a list of them on the=20 <a href=3D"/downloads/variants.html">Variants / Patches</a> |
|
From: Tom H. <th...@cy...> - 2006-07-14 03:06:54
|
Nightly build on ford ( i686, Fedora Core 4 ) started at 2006-07-14 03:25:21 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 235 tests, 5 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) |
|
From: <js...@ac...> - 2006-07-14 02:59:47
|
Nightly build on phoenix ( SuSE 10.0 ) started at 2006-07-14 03:30:01 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 == 235 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/leak-tree (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) |
|
From: Tom H. <to...@co...> - 2006-07-14 02:46:34
|
Nightly build on dunsmere ( athlon, Fedora Core 5 ) started at 2006-07-14 03:30:04 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 237 tests, 5 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-07-14 02:44:03
|
Nightly build on alvis ( i686, Red Hat 7.3 ) started at 2006-07-14 03:15:26 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 236 tests, 19 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/addressable (stderr) memcheck/tests/badjump (stderr) memcheck/tests/describe-block (stderr) memcheck/tests/erringfds (stderr) memcheck/tests/leak-0 (stderr) memcheck/tests/leak-cycle (stderr) memcheck/tests/leak-regroot (stderr) memcheck/tests/leak-tree (stderr) memcheck/tests/match-overrun (stderr) memcheck/tests/mempool (stderr) memcheck/tests/partial_load_dflt (stderr) memcheck/tests/partial_load_ok (stderr) memcheck/tests/partiallydefinedeq (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/sigkill (stderr) memcheck/tests/stack_changes (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-07-14 02:38:46
|
Nightly build on ginetta ( i686, Red Hat 8.0 ) started at 2006-07-14 03:10:16 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 236 tests, 6 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/mempool (stderr) memcheck/tests/pointer-trace (stderr) memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) memcheck/tests/xml1 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-07-14 02:37:05
|
Nightly build on dellow ( x86_64, Fedora Core 5 ) started at 2006-07-14 03:10:27 BST Results unchanged from 24 hours ago Checking out valgrind source tree ... done Configuring valgrind ... done Building valgrind ... done Running regression tests ... failed Regression test results follow == 260 tests, 2 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/x86/scalar (stderr) memcheck/tests/xml1 (stderr) |
|
From: Tom H. <th...@cy...> - 2006-07-14 02:18:06
|
Nightly build on gill ( x86_64, Fedora Core 2 ) started at 2006-07-14 03:00:22 BST Results differ from 24 hours ago Checking out valgrind source tree ... failed Last 20 lines of verbose log follow echo Checking out valgrind source tree ... svn co svn://svn.valgrind.org/valgrind/trunk -r {2006-07-14T03:00:22} valgrind svn: Can't connect to host 'svn.valgrind.org': No route to host ================================================= == 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 == 260 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == memcheck/tests/stack_switch (stderr) memcheck/tests/x86/scalar (stderr) memcheck/tests/x86/scalar_supp (stderr) none/tests/fdleak_fcntl (stderr) ================================================= == Difference between 24 hours ago and now == ================================================= *** old.short Fri Jul 14 03:18:43 2006 --- new.short Fri Jul 14 03:18:46 2006 *************** *** 1,14 **** ! Checking out valgrind source tree ... done ! Configuring valgrind ... done ! Building valgrind ... done ! Running regression tests ... failed ! Regression test results follow ! ! == 260 tests, 4 stderr failures, 0 stdout failures, 0 posttest failures == ! memcheck/tests/stack_switch (stderr) ! memcheck/tests/x86/scalar (stderr) ! memcheck/tests/x86/scalar_supp (stderr) ! none/tests/fdleak_fcntl (stderr) --- 1,7 ---- ! Checking out valgrind source tree ... failed ! Last 20 lines of verbose log follow echo + Checking out valgrind source tree ... svn co svn://svn.valgrind.org/valgrind/trunk -r {2006-07-14T03:00:22} valgrind + svn: Can't connect to host 'svn.valgrind.org': No route to host |
|
From: John R.
|
Bryan Meredith wrote: > What would be a good way to approach the project team as "your stuff > leaks here - my experimental tool says so (and so does this one)" is > probably not going to make me any friends... Perhaps they would be convinced by a simple test program (preferably short, too) that contains a loop which triggers the leak over and over. Use the "VIRT" column of the output from /usr/bin/top , or the "SZ" column of the output from "ps -l" to show that the process size is increasing when it should not. Then give them the patch that fixes the leak, and run the test program again, observing no increase in size. Wait until they ask, "Neat. How did you find the leak?" -- |
|
From: Nicholas N. <nj...@cs...> - 2006-07-14 01:12:39
|
On Thu, 13 Jul 2006, Bryan Meredith wrote: > What would be a good way to approach the project team as "your stuff > leaks here - my experimental tool says so (and so does this one)" is > probably not going to make me any friends... I don't think there's harm in telling people. It's just a bug report, people should be happy to get them, especially if it has good info on what the root cause is. You could say "your program has a leak here, and by the way I used my tool Omega to automatically find it". > Finally, how do I go about requesting a link to Omega be added to your > patches page and what criteria would I have to meet? There's no real criteria... I'm happy to add something to the Variants/Patches page. Can you give me a one sentence description and a URL to link to? Nick |