aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorLeena Miettinen <riitta-leena.miettinen@digia.com>2012-09-18 16:29:33 +0200
committerhjk <qthjk@ovi.com>2012-09-18 16:41:03 +0200
commit069b5a536d11a434e0a594bed9f544c8a1cc063f (patch)
tree6a533739e14bdfe8b20d36fc071787474e02bcaa /doc
parent25bb6712c61b1669e6f92f6ecc056773675da68f (diff)
Doc: memcheck requires a debug build
Make terminology more consistent and add link to glossary Change-Id: I46bbba560e14a917857cd89691986019d90b1550 Reviewed-by: hjk <qthjk@ovi.com>
Diffstat (limited to 'doc')
-rw-r--r--doc/src/analyze/creator-valgrind.qdoc11
1 files changed, 6 insertions, 5 deletions
diff --git a/doc/src/analyze/creator-valgrind.qdoc b/doc/src/analyze/creator-valgrind.qdoc
index 6ec02400da..5edf7b3bdc 100644
--- a/doc/src/analyze/creator-valgrind.qdoc
+++ b/doc/src/analyze/creator-valgrind.qdoc
@@ -45,7 +45,7 @@
\list 1
- \o In the \gui Projects mode, select a release build configuration.
+ \o In the \gui Projects mode, select a debug build configuration.
\o Select \gui Analyze to open the \gui Analyze mode.
@@ -166,12 +166,13 @@
the \gui Callers view and about the called functions in the \gui Callees
view.
- Since Debug and Release mode run-time characteristics differ
- significantly, analytical findings for one mode may or not be
- relevant for the other. Profiling a Debug mode build
+ Since the run-time characteristics of debug and release
+ \l{glossary-build-config}{build configurations}
+ differ significantly, analytical findings for one build configuration may or
+ not be relevant for the other. Profiling a debug build
often finds a major part of the time being spent in low-level
code like container implementations, while the same code
- does not show up in the profile of a Release build of the
+ does not show up in the profile of a release build of the
same application due to inlining and other optimizations
typically done there.