diff options
| author | Eike Ziller <eike.ziller@theqtcompany.com> | 2015-08-20 13:23:06 +0200 |
|---|---|---|
| committer | Eike Ziller <eike.ziller@theqtcompany.com> | 2015-08-20 13:23:13 +0200 |
| commit | 8eaaef96aa55c10f00b429c3e6ade8d8be568141 (patch) | |
| tree | 33ff4239b1523d5f145d0ec5681716859f276e4c /doc | |
| parent | 2f781ac28083bc06b549ce69335b4c7901cde61d (diff) | |
| parent | 0173c638537e9a53a439ec4be5a9ab7b10a27a79 (diff) | |
Merge remote-tracking branch 'origin/3.5'
Change-Id: I65968dd02ea6bdd15f304ae567dd0c02238e6949
Diffstat (limited to 'doc')
| -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 095cc7fe4c..8025f47159 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 |