|
From: <sv...@va...> - 2005-11-18 22:09:49
|
Author: njn Date: 2005-11-18 22:09:47 +0000 (Fri, 18 Nov 2005) New Revision: 5200 Log: Minor QSG tweaks. Modified: trunk/docs/xml/quick-start-guide.xml Modified: trunk/docs/xml/quick-start-guide.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=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/xml/quick-start-guide.xml 2005-11-18 21:32:18 UTC (rev 519= 9) +++ trunk/docs/xml/quick-start-guide.xml 2005-11-18 22:09:47 UTC (rev 520= 0) @@ -175,7 +175,7 @@ </listitem> </itemizedlist> =20 -If you don't understand an error message, please consult +If you don't understand an error message, please consult=20 <xref linkend=3D"mc-manual.errormsgs"/> in the <xref linkend=3D"manual"/= > which has examples of all the error messages Memcheck produces.</para> </sect1> @@ -183,11 +183,14 @@ <sect1 id=3D"quick-start.caveats" xreflabel=3D"Caveats"> <title>Caveats</title> <para>Memcheck is not perfect; it occasionally produces false positives= , -and there are mechanisms for suppressing these (see +and there are mechanisms for suppressing these (see=20 <xref linkend=3D"manual-core.suppress"/> in the <xref linkend=3D"manual"= />). 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?</para> +messages produced by a compiler, right? The suppression mechanism is al= so +useful if Memcheck is reporting errors in library code that you cannot +change; the default suppression set hides a lot of these, but you may +come across more.</para> =20 <para>Memcheck also cannot detect every memory error your program has. = For example, it can't detect if you overrun the bounds of an array that is |