zenithsiz/ftmemsim-valgrind
1
0
Fork 0
mirror of https://github.com/Zenithsiz/ftmemsim-valgrind.git synced 2026-02-09 05:10:23 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Minor QSG tweaks.

Browse Source 
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5200
This commit is contained in:
Nicholas Nethercote
2005-11-18 22:09:47 +00:00
parent 7f18ebbc33
commit cc64c8dda4
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
docs/xml/quick-start-guide.xml
View File

@@ -175,7 +175,7 @@ Memcheck cannot tell you why the memory leaked, unfortunately. (Ignore the
</listitem>
</itemizedlist>
If you don't understand an error message, please consult
If you don't understand an error message, please consult
<xref linkend="mc-manual.errormsgs"/> in the <xref linkend="manual"/> which has
examples of all the error messages Memcheck produces.</para>
</sect1>
@@ -183,11 +183,14 @@ examples of all the error messages Memcheck produces.</para>
<sect1 id="quick-start.caveats" xreflabel="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
<xref linkend="manual-core.suppress"/> in the <xref linkend="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 also
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>
<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