diff options
| author | Ulf Hermann <ulf.hermann@theqtcompany.com> | 2015-08-11 10:59:33 +0200 |
|---|---|---|
| committer | Ulf Hermann <ulf.hermann@theqtcompany.com> | 2015-08-11 11:16:01 +0000 |
| commit | f99e40602bc4757cf9893da39799b1dcbe240112 (patch) | |
| tree | ee6814c317487372ba5080106654b0bd3d01d667 /doc/src/analyze | |
| parent | 472d584d5dc22c88c45acb257703bcbdbcdc0bdd (diff) | |
Fix typos in CPU Usage Analyzer docs
Change-Id: Ie1f62224b62a148c0a6df1ff4afb55fa9aec89af
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@theqtcompany.com>
Diffstat (limited to 'doc/src/analyze')
| -rw-r--r-- | doc/src/analyze/cpu-usage-analyzer.qdoc | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/doc/src/analyze/cpu-usage-analyzer.qdoc b/doc/src/analyze/cpu-usage-analyzer.qdoc index 095cc7fe4c8..8025f471593 100644 --- a/doc/src/analyze/cpu-usage-analyzer.qdoc +++ b/doc/src/analyze/cpu-usage-analyzer.qdoc @@ -198,14 +198,14 @@ As the Perf tool only provides periodic samples, the CPU Usage Analyzer cannot determine the exact time when a function was called or when it - returned. You can, however, see exactly when a sample was taken on the + returned. You can, however, see exactly when a sample was taken in the second row of each thread. The CPU Usage Analyzer assumes that if the same - function is present in the same place in the call chain in multiple samples - on a row, then this represents a single call to the respective function. - This is, of course, a simplification. Also, there may be other functions - being called between the samples taken, which do not show up in the profile - data. However, statistically, the data is likely to show the functions that - spend the most CPU time most prominently. + function is present at the same place in the call chain in multiple + consecutive samples, then this represents a single call to the respective + function. This is, of course, a simplification. Also, there may be other + functions being called between the samples taken, which do not show up in + the profile data. However, statistically, the data is likely to show the + functions that spend the most CPU time most prominently. If a function without debug information is encountered, further unwinding of the stack may fail. Unwinding will also fail if a QML or JavaScript @@ -254,7 +254,7 @@ Start Board and SILICA Architect Tibidabo, are correctly set up for profiling in the dwarf mode. For other devices, check whether Perf can read back its own data in a sensible way by checking the output of - \c {perf report} or \c {perf script} in the recorded Perf data files. + \c {perf report} or \c {perf script} for the recorded Perf data files. \section1 Troubleshooting |