aboutsummaryrefslogtreecommitdiffstats
path: root/doc/src/analyze
diff options
context:
space:
mode:
Diffstat (limited to 'doc/src/analyze')
-rw-r--r--doc/src/analyze/creator-analyze.qdoc4
-rw-r--r--doc/src/analyze/creator-valgrind-overview.qdoc6
-rw-r--r--doc/src/analyze/creator-valgrind.qdoc38
-rw-r--r--doc/src/analyze/qtquick-profiler.qdoc26
4 files changed, 37 insertions, 37 deletions
diff --git a/doc/src/analyze/creator-analyze.qdoc b/doc/src/analyze/creator-analyze.qdoc
index c130cd29983..8a004665f5e 100644
--- a/doc/src/analyze/creator-analyze.qdoc
+++ b/doc/src/analyze/creator-analyze.qdoc
@@ -49,14 +49,14 @@
\list
- \o \l{Profiling QML Applications}{QML Profiler}
+ \li \l{Profiling QML Applications}{QML Profiler}
You can inspect binding evaluations, signal handling, and
painting operations when running QML code. This is useful for
identifying potential bottlenecks, especially in the evaluation
of bindings.
- \o \l{Using Valgrind Code Analysis Tools}{Valgrind Code Analysis Tools}
+ \li \l{Using Valgrind Code Analysis Tools}{Valgrind Code Analysis Tools}
You can detect problems in memory management by using the Memcheck
tool and find cache misses in the code by using the Callgrind tool.
diff --git a/doc/src/analyze/creator-valgrind-overview.qdoc b/doc/src/analyze/creator-valgrind-overview.qdoc
index 6b903c96fdc..820b0cb9c72 100644
--- a/doc/src/analyze/creator-valgrind-overview.qdoc
+++ b/doc/src/analyze/creator-valgrind-overview.qdoc
@@ -50,11 +50,11 @@
\list
- \o \l{Detecting Memory Leaks}
+ \li \l{Detecting Memory Leaks}
- \o \l{Profiling Function Execution}
+ \li \l{Profiling Function Execution}
- \o \l{Running Valgrind Tools Remotely}
+ \li \l{Running Valgrind Tools Remotely}
\endlist
diff --git a/doc/src/analyze/creator-valgrind.qdoc b/doc/src/analyze/creator-valgrind.qdoc
index f317549a9f8..c2a805c1808 100644
--- a/doc/src/analyze/creator-valgrind.qdoc
+++ b/doc/src/analyze/creator-valgrind.qdoc
@@ -44,19 +44,19 @@
\list 1
- \o In the \gui Projects mode, select a debug build configuration.
+ \li In the \gui Projects mode, select a debug build configuration.
- \o Select \gui Analyze to open the \gui Analyze mode.
+ \li Select \gui Analyze to open the \gui Analyze mode.
- \o Select \gui {Analyze Memory} on the toolbar.
+ \li Select \gui {Analyze Memory} on the toolbar.
- \o Select the
+ \li Select the
\inlineimage qtcreator-analyze-start-button.png "Start button"
button to start the application.
- \o Use the application to analyze it.
+ \li Use the application to analyze it.
- \o Select the
+ \li Select the
\inlineimage qtcreator-debug-button-stop.png "Stop button"
button to view the results of the analysis in the
\gui {Analysis} view.
@@ -135,19 +135,19 @@
\list 1
- \o In the \gui Projects mode, select a release build configuration.
+ \li In the \gui Projects mode, select a release build configuration.
- \o Select \gui Analyze to open the \gui Analyze mode.
+ \li Select \gui Analyze to open the \gui Analyze mode.
- \o Select \gui Profile on the toolbar.
+ \li Select \gui Profile on the toolbar.
- \o Select the
+ \li Select the
\inlineimage qtcreator-analyze-start-button.png "Start button"
button to start the application.
- \o Use the application to analyze it.
+ \li Use the application to analyze it.
- \o Select the
+ \li Select the
\inlineimage qtcreator-debug-button-stop.png "Stop button"
button to view the results of the analysis in the \gui Profile
view.
@@ -209,11 +209,11 @@
\list
- \o Cache misses on instruction reads (I1mr/I2mr)
+ \li Cache misses on instruction reads (I1mr/I2mr)
- \o Data read accesses (Dr) and related cache misses (D1mr/D2mr)
+ \li Data read accesses (Dr) and related cache misses (D1mr/D2mr)
- \o Data write accesses (Dw) and related cache misses (D1mw/D2mw)
+ \li Data write accesses (Dw) and related cache misses (D1mw/D2mw)
\endlist
@@ -224,10 +224,10 @@
\list
- \o Number of conditional branches executed and related predictor misses
+ \li Number of conditional branches executed and related predictor misses
(Bc/Bcm)
- \o Executed indirect jumps and related misses of the jump address
+ \li Executed indirect jumps and related misses of the jump address
predictor (Bi/Bim)
\endlist
@@ -252,12 +252,12 @@
\list 1
- \o Select \gui {Analyze > Valgrind Memory Analyzer (External)} or
+ \li Select \gui {Analyze > Valgrind Memory Analyzer (External)} or
\gui {Valgrind Function Profiler (External)}.
\image qtcreator-valgrind-remote-settings.png "Start Analyzer dialog"
- \o Specify the application to run and analyze, and the \l{glossary-buildandrun-kit}{kit}
+ \li Specify the application to run and analyze, and the \l{glossary-buildandrun-kit}{kit}
to use.
\endlist
diff --git a/doc/src/analyze/qtquick-profiler.qdoc b/doc/src/analyze/qtquick-profiler.qdoc
index 262e06f8d8a..782972b1243 100644
--- a/doc/src/analyze/qtquick-profiler.qdoc
+++ b/doc/src/analyze/qtquick-profiler.qdoc
@@ -34,20 +34,20 @@
\list 1
- \o To be able to profile an application, you must set up QML debugging
+ \li To be able to profile an application, you must set up QML debugging
for the project. For more information, see
\l{Setting Up QML Debugging}.
- \o In the \gui Projects mode, select Qt 4.7.4 in the \gui {Qt version}
+ \li In the \gui Projects mode, select Qt 4.7.4 in the \gui {Qt version}
field.
\note To profile applications on devices, you must install Qt 4.7.4
or later libraries on them.
- \o Select \gui {Analyze > QML Profiler} to profile the current
+ \li Select \gui {Analyze > QML Profiler} to profile the current
application.
- \o Select the
+ \li Select the
\inlineimage qtcreator-analyze-start-button.png
(\gui Start) button to start the application from the
QML Profiler.
@@ -99,17 +99,17 @@
\list
- \o Painting operations
+ \li Painting operations
- \o Compiling the QML sources
+ \li Compiling the QML sources
- \o Creating elements
+ \li Creating elements
- \o Binding evaluations
+ \li Binding evaluations
- \o Signal handling
+ \li Signal handling
- \o Summary of the recorded period
+ \li Summary of the recorded period
\endlist
@@ -205,11 +205,11 @@
\list 1
- \o Select \gui {Projects > Run}.
+ \li Select \gui {Projects > Run}.
- \o In \gui {Run Environment}, click \gui Add.
+ \li In \gui {Run Environment}, click \gui Add.
- \o Add the QML_DISABLE_OPTIMIZER variable and set its value to 1.
+ \li Add the QML_DISABLE_OPTIMIZER variable and set its value to 1.
\endlist