summaryrefslogtreecommitdiffstats
path: root/kmtrace
diff options
context:
space:
mode:
authorTimothy Pearson <kb9vqf@pearsoncomputing.net>2013-01-20 00:23:32 -0600
committerTimothy Pearson <kb9vqf@pearsoncomputing.net>2013-01-20 00:23:32 -0600
commit94c9dc38220d50d037075127ad46add8a264ef26 (patch)
treeaf6ba5d26197827dac1b1901895dee7a7b62a9d6 /kmtrace
parent479647c43c62fc50302342c8ac50a2fe024b4426 (diff)
downloadtdesdk-94c9dc38220d50d037075127ad46add8a264ef26.tar.gz
tdesdk-94c9dc38220d50d037075127ad46add8a264ef26.zip
Rename KApplication to TDEApplication to avoid conflicts with KDE4
Diffstat (limited to 'kmtrace')
-rw-r--r--kmtrace/README6
1 files changed, 3 insertions, 3 deletions
diff --git a/kmtrace/README b/kmtrace/README
index 67330fe4..6084b2b7 100644
--- a/kmtrace/README
+++ b/kmtrace/README
@@ -18,7 +18,7 @@ There are two ways to activate memory usage loggings by ktrace :
1) The LD_PRELOAD way
This way, you can debug any application without having to recompile it,
-but you'll have to debug also the memory allocated by KApplication and
+but you'll have to debug also the memory allocated by TDEApplication and
friends.
You can activate malloc logging by starting yourApplication as:
@@ -57,8 +57,8 @@ to add any commandline options.
TIPS
====
-* If you can't be bothered with the stuff that KApplication allocates for you
-you might want to put the ktrace() call after the KApplication constructor.
+* If you can't be bothered with the stuff that TDEApplication allocates for you
+you might want to put the ktrace() call after the TDEApplication constructor.
This will lead to a lot of warnings like:
Freeing unalloacted memory: 0x08056108