feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity

Doc: memcheck requires a debug build

Browse Source 
Make terminology more consistent and add link to glossary

Change-Id: I46bbba560e14a917857cd89691986019d90b1550
Reviewed-by: hjk <qthjk@ovi.com>
This commit is contained in:
Leena Miettinen
2012-09-18 16:29:33 +02:00
committed by hjk
parent 25bb6712c6
commit 069b5a536d
1 changed files with 6 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
doc/src/analyze/creator-valgrind.qdoc
View File

@@ -45,7 +45,7 @@
\list 1 \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. \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 the \gui Callers view and about the called functions in the \gui Callees
view. view.
Since Debug and Release mode run-time characteristics differ Since the run-time characteristics of debug and release
significantly, analytical findings for one mode may or not be \l{glossary-build-config}{build configurations}
relevant for the other. Profiling a Debug mode build 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 often finds a major part of the time being spent in low-level
code like container implementations, while the same code 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 same application due to inlining and other optimizations
typically done there. typically done there.