[Valgrind-developers] valgrind-www r273 - trunk/info

[<sv...@va...>]

Author: njn
Date: 2006-03-31 13:24:48 +0100 (Fri, 31 Mar 2006)
New Revision: 273

Log:
update memcheck description

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-03-27 12:02:53 UTC (rev 272)
+++ trunk/info/tools.html	2006-03-31 12:24:48 UTC (rev 273)
@@ -1,6 +1,6 @@
 <h1>Valgrind's Tool Suite</h1>
=20
-<p>The Valgrind distribution includes five useful debugging and
+<p>The Valgrind distribution includes four useful debugging and
 profiling tools:</p>
=20
 <div id=3D"pagemenu">
@@ -25,17 +25,16 @@
 primarily at C and C++ programs. When a program is run under
 Memcheck's supervision, all reads and writes of memory are
 checked, and calls to malloc/new/free/delete are intercepted. As
-a result, Memcheck can detect:</p>
+a result, Memcheck can detect if your program:</p>
 <ul>
-<li>Use of uninitialised memory</li>
-<li>Reading/writing memory after it has been free'd</li>
-<li>Reading/writing off the end of malloc'd blocks</li>
-<li>Reading/writing inappropriate areas on the stack</li>
-<li>Memory leaks -- where pointers to malloc'd blocks are lost forever</=
li>
-<li>Passing of uninitialised and/or unaddressible memory to system calls=
</li>
-<li>Mismatched use of malloc/new/new [] vs free/delete/delete []</li>
-<li>Overlapping src and dst pointers in memcpy() and related functions</=
li>
-<li>Some misuses of the POSIX pthreads API</li>
+<li>Accesses memory it shouldn't (areas not yet allocated, areas that ha=
ve
+    been freed, areas past the end of heap blocks, inaccessible areas of
+    the stack).</li>
+<li>Uses uninitialised values in dangerous ways.</li>
+<li>Leaks memory.</li>
+<li>Does bad frees of heap blocks (double frees, mismatched frees).</li>
+<li>Passes overlapping source and destination memory blocks to memcpy() =
and
+    related functions.</li>
 </ul>
=20
 <p>Memcheck reports these errors as soon as they occur, giving