|
From: <sv...@va...> - 2006-03-27 12:03:07
|
Author: njn Date: 2006-03-27 13:02:53 +0100 (Mon, 27 Mar 2006) New Revision: 272 Log: Bye-bye Addrcheck. Modified: trunk/info/about.html trunk/info/tools.html Modified: trunk/info/about.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/about.html 2006-03-16 00:33:30 UTC (rev 271) +++ trunk/info/about.html 2006-03-27 12:02:53 UTC (rev 272) @@ -123,7 +123,7 @@ =20 <li>All the time. For small programs with short run-times, when developing you can always run the program under a Valgrind tool -(usually either Memcheck or Addrcheck), knowing that memory bugs +(usually Memcheck), knowing that memory bugs will be found immediately.</li> =20 <li>In automatic testing. By using Valgrind tools in your 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-03-16 00:33:30 UTC (rev 271) +++ trunk/info/tools.html 2006-03-27 12:02:53 UTC (rev 272) @@ -7,7 +7,6 @@ <ul> <li> </li> <li><a href=3D"#memcheck">Memcheck</a></li> - <li><a href=3D"#addrcheck">Addrcheck</a></li> <li><a href=3D"#cachegrind">Cachegrind</a></li> <li><a href=3D"#massif">Massif</a></li> <li><a href=3D"#helgrind">Helgrind</a></li> @@ -49,20 +48,6 @@ than normal.</p> =20 =20 -<a name=3D"addrcheck"></a> -<h3>Addrcheck</h3> - -<p>Addrcheck is a lightweight version of Memcheck which does no -uninitialised-value checking. So it detects fewer errors than -Memcheck, but programs run about twice as fast as they do on -memcheck (about 5--20x slower than normal), and a lot less memory -is used. We have run entire KDE sessions under Addrcheck. This -means you can run programs for longer, and cover more test -scenarios. And it still finds lot of important bugs! You might -like to use Addrcheck most of the time for finding memory bugs, -and occasionally use Memcheck for more thorough checking.</p> - - <a name=3D"cachegrind"></a> <h3>Cachegrind</h3> =20 |