diff options
| author | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2012-01-30 11:57:55 -0600 |
|---|---|---|
| committer | Timothy Pearson <kb9vqf@pearsoncomputing.net> | 2012-01-30 11:57:55 -0600 |
| commit | dc0f665d4aa9587390d84153858f56a3d58e52e9 (patch) | |
| tree | 7c861c33363205e14d2ec97294f3040415c8aeb8 | |
| parent | 6d12e19c8a818f962b520995842d3ce218051f05 (diff) | |
| download | digikam-dc0f665d4aa9587390d84153858f56a3d58e52e9.tar.gz digikam-dc0f665d4aa9587390d84153858f56a3d58e52e9.zip | |
Rename ksocket and kcache
| -rw-r--r-- | HACKING | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -252,9 +252,9 @@ valgrind --tool=callgrind --instr-atstart=no digikam and prepare the situation you want to profile. Then, in another console, start profiling with "callgrind_control -i on" and, after the situation has passed, request a profile dump with "callgrind_control -d". -The resulting callgrind.out files need to be viewed with the kcachegrind program, e.g.: +The resulting callgrind.out files need to be viewed with the tdecachegrind program, e.g.: -kcachegrind callgrind.out.16693.1 +tdecachegrind callgrind.out.16693.1 ================================================================================= API Documentation Validation, User Documentation Validation, Source Code Checking |