diff options
| author | Leena Miettinen <riitta-leena.miettinen@digia.com> | 2013-11-20 17:09:11 +0100 |
|---|---|---|
| committer | Leena Miettinen <riitta-leena.miettinen@digia.com> | 2013-11-21 10:09:00 +0100 |
| commit | 1f837610facef06c9e835f0421da86113e948069 (patch) | |
| tree | 4682da0ecba2ffd3f94a28f76e900124ba3929a3 /doc | |
| parent | 5e1d6fcfe8b41167da1e4c7f486d14b7dc2d93fe (diff) | |
Doc: new Memcheck options
Update screenshots.
Change-Id: I45e0404e9213be3bae526607d55453cf53d8ea80
Reviewed-by: hjk <hjk121@nokiamail.com>
Diffstat (limited to 'doc')
| -rwxr-xr-x[-rw-r--r--] | doc/images/analyzer-issues.png | bin | 18296 -> 75473 bytes | |||
| -rwxr-xr-x[-rw-r--r--] | doc/images/qtcreator-valgrind-memcheck-options.png | bin | 4070 -> 28803 bytes | |||
| -rw-r--r-- | doc/src/analyze/creator-valgrind.qdoc | 19 |
3 files changed, 19 insertions, 0 deletions
diff --git a/doc/images/analyzer-issues.png b/doc/images/analyzer-issues.png Binary files differindex c60f86607c..7bcaeeecf6 100644..100755 --- a/doc/images/analyzer-issues.png +++ b/doc/images/analyzer-issues.png diff --git a/doc/images/qtcreator-valgrind-memcheck-options.png b/doc/images/qtcreator-valgrind-memcheck-options.png Binary files differindex baca54ecf6..a102b61367 100644..100755 --- a/doc/images/qtcreator-valgrind-memcheck-options.png +++ b/doc/images/qtcreator-valgrind-memcheck-options.png diff --git a/doc/src/analyze/creator-valgrind.qdoc b/doc/src/analyze/creator-valgrind.qdoc index b0272c9a3f..7d00ae9792 100644 --- a/doc/src/analyze/creator-valgrind.qdoc +++ b/doc/src/analyze/creator-valgrind.qdoc @@ -97,6 +97,25 @@ uninitialized memory} check box is selected by default. You can deselect it to make Memcheck run faster. + Memcheck searches for memory leaks when the client application finishes. To + view the amount of leaks that occurred, select \gui {Summary Only} in the + \gui {Check for leaks on finish} field. To also view details of each leak, + select \gui Full. + + \section2 Showing Reachable and Indirectly Lost Blocks + + \e Reachable blocks are blocks that are pointed at by a pointer or chain + of pointers and that might have been freed before the application exited. + \e {Indirectly lost} blocks are considered lost because all the blocks that + point to them are themselves lost. For example, all the children of a lost + root node are indirectly lost. + + By default, Memcheck does not report reachable and indirectly lost blocks. + To have them reported, select the \gui {Show reachable and indirectly lost + blocks}. + + \section2 Suppressing Errors + Memcheck detects numerous problems in the system libraries, such as the C library, which come pre-installed with your OS. As you cannot easily fix them, you want to suppress them. Valgrind reads a list of errors to suppress |
