Rename ksocket and kcache

pull/1/head
Timothy Pearson 13 years ago
parent 53b45e0887
commit 2020f146a7

@ -9,4 +9,4 @@
#
#################################################
tde_create_handbook( DESTINATION kcachegrind )
tde_create_handbook( DESTINATION tdecachegrind )

@ -1,12 +1,12 @@
<?xml version="1.0" ?>
<!DOCTYPE book PUBLIC "-//KDE//DTD DocBook XML V4.2-Based Variant V1.1//EN" "dtd/kdex.dtd" [
<!ENTITY kcachegrind '<application>KCachegrind</application>'>
<!ENTITY tdecachegrind '<application>KCachegrind</application>'>
<!ENTITY cachegrind "<application>Cachegrind</application>">
<!ENTITY calltree "<application>Calltree</application>">
<!ENTITY callgrind "<application>Callgrind</application>">
<!ENTITY valgrind "<application>Valgrind</application>">
<!ENTITY oprofile "<application>OProfile</application>">
<!ENTITY kappname "&kcachegrind;">
<!ENTITY kappname "&tdecachegrind;">
<!ENTITY package "tdesdk">
<!ENTITY % addindex "IGNORE">
<!ENTITY % English "INCLUDE">
@ -17,7 +17,7 @@
<book lang="&language;">
<bookinfo>
<title>The &kcachegrind; Handbook</title>
<title>The &tdecachegrind; Handbook</title>
<authorgroup>
<author>
@ -43,7 +43,7 @@
<abstract>
<para>
&kcachegrind; is a profile data visualization tool, written using the &kde; environment.
&tdecachegrind; is a profile data visualization tool, written using the &kde; environment.
</para>
</abstract>
@ -186,14 +186,14 @@ Besides a list of functions sorted according exclusive or inclusive cost metrics
</sect1>
</chapter>
<chapter id="using-kcachegrind">
<title>Using &kcachegrind;</title>
<chapter id="using-tdecachegrind">
<title>Using &tdecachegrind;</title>
<sect1 id="using-profile">
<title>Generate Data to Visualize</title>
<para>First, one wants to generate performance data by measuring aspects of the
runtime characteristics of an application, using a profiling tool. &kcachegrind;
runtime characteristics of an application, using a profiling tool. &tdecachegrind;
itself does not include any profiling tool, but is good in being used together with
&callgrind;, and by using a converter, also can be used to visualize data produced
with &oprofile;. Although the scope of this manual is not to document profiling
@ -205,8 +205,8 @@ with these tools, the next section provides short quickstart tutorials to get yo
<para>
&callgrind; is available from
<ulink url="http://kcachegrind.sf.net">
http://kcachegrind.sf.net</ulink>.
<ulink url="http://tdecachegrind.sf.net">
http://tdecachegrind.sf.net</ulink>.
Note that it previously was called &calltree;, but that name was misleading.
</para>
@ -217,7 +217,7 @@ Most common use is to prefix the command line to start your application with
<blockquote><para><command>callgrind myprogram myargs</command></para></blockquote>
At program termination, a file <filename>callgrind.out.pid</filename> will be
generated which can be loaded into &kcachegrind;.
generated which can be loaded into &tdecachegrind;.
</para>
<para>
@ -234,7 +234,7 @@ callgrind --dump-before=KonqMainWindow::slotReload konqueror </command></para></
This will produce multiple profile data files with an additional
sequential number at the end of the filename. A file without such an
number at the end (only ending in the process PID) will also be produced;
by loading this file into &kcachegrind;, all others are loaded too, and can
by loading this file into &tdecachegrind;, all others are loaded too, and can
be seen in the Parts Overview and Parts list.
</para>
@ -256,14 +256,14 @@ as all actions on the system can be observed; therefore, the following has to be
First, configure the profiling process, using the GUI <command>oprof_start</command> or the
command-line tool opcontrol. Standard configuration should be timer mode (TBS, see introduction). To start the measurement, run
<command>opcontrol -s</command>. Then run the application you are interested in and, afterwards, do a <command>opcontrol -d</command>. This will write out
the measurement results into files under directory <filename>/var/lib/oprofile/samples/</filename>. To be able to visualize the data in &kcachegrind;, do in an empty directory:
the measurement results into files under directory <filename>/var/lib/oprofile/samples/</filename>. To be able to visualize the data in &tdecachegrind;, do in an empty directory:
<blockquote><para><command>
opreport -gdf | op2callgrind
</command></para></blockquote>
This will produce a lot of files, one for every program which was running
on the system. Each one can be loaded into &kcachegrind; on its own.
on the system. Each one can be loaded into &tdecachegrind; on its own.
</para>
</sect2>
@ -273,7 +273,7 @@ on the system. Each one can be loaded into &kcachegrind; on its own.
<title>User Interface Basics</title>
<para>
When starting &kcachegrind; with a profile data file as argument, or after loading one with File/Open, you will see a sidebar containing the function list
When starting &tdecachegrind; with a profile data file as argument, or after loading one with File/Open, you will see a sidebar containing the function list
at the left; and, on the right the main part, an area with visualizations for
a selected function. This visualization area can be arbitrarily configured to
show multiple visualizations at once.
@ -297,20 +297,20 @@ A first overview of the runtime characteristics should be given when you select
<para>
To explore the GUI further, in addition to this manual, also have a look at the documentation section on the web site
<ulink url="http://kcachegrind.sf.net">
http://kcachegrind.sf.net</ulink>.
<ulink url="http://tdecachegrind.sf.net">
http://tdecachegrind.sf.net</ulink>.
Also,
every widget in &kcachegrind; has <quote>What's this</quote> help.
every widget in &tdecachegrind; has <quote>What's this</quote> help.
</para>
</sect1>
</chapter>
<chapter id="kcachegrind-concepts">
<chapter id="tdecachegrind-concepts">
<title>Basic Concepts</title>
<para>This chapter explains some concepts of the &kcachegrind;, and
<para>This chapter explains some concepts of the &tdecachegrind;, and
introduces terms used in the interface.
</para>
@ -618,8 +618,8 @@ Select such a call information line to activate the call destination.
<chapter id="commands">
<title>Command Reference</title>
<sect1 id="kcachegrind-mainwindow">
<title>The main &kcachegrind; window</title>
<sect1 id="tdecachegrind-mainwindow">
<title>The main &tdecachegrind; window</title>
<para></para>
<sect2>
@ -768,14 +768,14 @@ This is most interesting after another profile data file was generated for an al
<qandaentry>
<question>
<para>
What is &kcachegrind; for? I have no idea.
What is &tdecachegrind; for? I have no idea.
</para>
</question>
<answer>
<para>
&kcachegrind; is a helpful at a later stage in software development,
&tdecachegrind; is a helpful at a later stage in software development,
called Profiling. If you don't develop applications, you don't need
&kcachegrind;.
&tdecachegrind;.
</para>
</answer>
</qandaentry>
@ -896,15 +896,15 @@ users.
<appendix id="installation">
<title>Installation</title>
<sect1 id="getting-kcachegrind">
<title>How to obtain &kcachegrind;</title>
<sect1 id="getting-tdecachegrind">
<title>How to obtain &tdecachegrind;</title>
<para>
&kcachegrind; is part of the &package; package of &kde;. For less supported
&tdecachegrind; is part of the &package; package of &kde;. For less supported
interim releases, &callgrind; and further documentation, see
the homepage at
<ulink url="http://kcachegrind.sf.net">
http://kcachegrind.sf.net</ulink>. Look there for
<ulink url="http://tdecachegrind.sf.net">
http://tdecachegrind.sf.net</ulink>. Look there for
further installation and compile instructions.
</para>
</sect1>
@ -913,7 +913,7 @@ further installation and compile instructions.
<title>Requirements</title>
<para>
In order to successfully use &kcachegrind;, you need &kde; 3.x. For
In order to successfully use &tdecachegrind;, you need &kde; 3.x. For
generating profile data, &cachegrind; or &calltree;/&callgrind; is recommend.
</para>
</sect1>

@ -7,7 +7,7 @@
with grouping on
2004/04/28
* toplevel.h/cpp, kcachegrindui.rc
* toplevel.h/cpp, tdecachegrindui.rc
- Switching Layouts
* multiview.cpp: Removed some qDebug's
* Same term fixes

@ -1,6 +1,6 @@
SUBDIRS = kcachegrind pics converters
SUBDIRS = tdecachegrind pics converters
EXTRA_DIST = \
AUTHORS COPYING NEWS ChangeLog INSTALL README TODO \
kcachegrind.lsm kcachegrind.spec version.h
tdecachegrind.lsm tdecachegrind.spec version.h

@ -54,7 +54,7 @@ KCachegrind features
Most important: TreeMap calltree visualisation.
For the rest, see the detailed "What's this?" help for
each part of KCachegrind and the quick starter on the
WWW page ( http://kcachegrind.sourceforge.net/cgi-bin/show.cgi )
WWW page ( http://tdecachegrind.sourceforge.net/cgi-bin/show.cgi )

@ -1,8 +1,8 @@
KCACHEGRIND_VERSION=0.4.6kde
AC_SUBST(KCACHEGRIND_VERSION)
TDECACHEGRIND_VERSION=0.4.6kde
AC_SUBST(TDECACHEGRIND_VERSION)
AC_FUNC_MMAP
dnl AC_OUTPUT( kcachegrind/version.h )
dnl AC_OUTPUT( kcachegrind/kcachegrind.spec )
dnl AC_OUTPUT( kcachegrind/kcachegrind.lsm )
dnl AC_OUTPUT( tdecachegrind/version.h )
dnl AC_OUTPUT( tdecachegrind/tdecachegrind.spec )
dnl AC_OUTPUT( tdecachegrind/tdecachegrind.lsm )

@ -18,7 +18,7 @@ Thanks go to
hotshot2calltree
If you want to write a converter, have a look at the calltree format
description on the web site (kcachegrind.sf.net).
description on the web site (tdecachegrind.sf.net).
Josef

@ -53,7 +53,7 @@
# This creates a cachegrind-style file called cachgrind.out.tmon.out or
# cachegrind.out.foo, respecitvely.
#
# 3) Run kcachegrind cachegrind.out.foo
# 3) Run tdecachegrind cachegrind.out.foo
#
# 4) Enjoy!
@ -171,7 +171,7 @@ foreach my $specifier ( keys %$tree ) {
}
$output .= "\n";
}
print STDERR "Writing kcachegrind output to $outfile\n";
print STDERR "Writing tdecachegrind output to $outfile\n";
$outfd->print($output);

@ -21,7 +21,7 @@
#
#
# This script transforms the pstat output of the hotshot
# python profiler into the input of kcachegrind.
# python profiler into the input of tdecachegrind.
#
# example usage:
# modify you python script to run this code:
@ -40,8 +40,8 @@
# or here:
# hotshot2cachegrind cachegrind.out.0 pythongrind.prof
#
# then call kcachegrind:
# kcachegrind cachegrind.out.0
# then call tdecachegrind:
# tdecachegrind cachegrind.out.0
#
# TODO:
# * es gibt Probleme mit rekursiven (direkt und indirekt) Aufrufen - dann
@ -140,7 +140,7 @@ def updateStatus(filecount):
sys.stdout.write("reading File #%d \r" % filecount)
sys.stdout.flush()
def convertProfFiles(output, inputfilenames):
"""convert all the given input files into one kcachegrind
"""convert all the given input files into one tdecachegrind
input file.
"""
call_dict = {}
@ -207,7 +207,7 @@ def handleCostPerPos(cost_per_pos, pos, current_cost):
cost_per_pos[filename] = file_dict
def convertProfFile(inputfilename, caller_stack, call_dict, cost_per_pos, cost_per_function):
"""convert a single input file into one kcachegrind
"""convert a single input file into one tdecachegrind
data.
this is the most expensive function in this python source :-)
@ -276,7 +276,7 @@ class TagWriter:
# self.output.write("%s=%s\n" % (tag, value))
def dumpResults(output, call_dict, total_cost, cost_per_pos, cost_per_function):
"""write the collected results in the format kcachegrind
"""write the collected results in the format tdecachegrind
could read.
"""
# the intro
@ -319,7 +319,7 @@ def dumpResults(output, call_dict, total_cost, cost_per_pos, cost_per_function):
output.write("calls=%d\n%d %d\n" % (count, caller_x[1], cost))
tagwriter.clear()
#tagwriter.clearTag("cob")
# is it a bug in kcachegrind, that the "cob=xxx" line has
# is it a bug in tdecachegrind, that the "cob=xxx" line has
# to be rewritten after a calls entry with costline ?
#assert cost <= total_cost, "caller_x: %s, per_caller_dict: %s " % (caller_x, per_caller_dict, )
#output.write("calls=%d\n%d %d\n" % (count, caller_x[1], cost))

@ -34,7 +34,7 @@
# and is provided completely free and without any warranty.
#
# This script is designed to convert the pprof output from
# APD (http://pecl.php.net/apd/) to one readable by kcachegrind. To use
# APD (http://pecl.php.net/apd/) to one readable by tdecachegrind. To use
# this script:
#
# 1) Install APD.
@ -204,7 +204,7 @@ foreach($tree as $caller => $data) {
}
print "\ntotals=$total_cost\n";
$buffer = ob_get_clean();
print "Writing kcachegrind compatible output to $outfile\n";
print "Writing tdecachegrind compatible output to $outfile\n";
fwrite($OUT, $buffer);
function usage()

@ -1,11 +1,11 @@
Begin3
Title: kcachegrind
Version: @KCACHEGRIND_VERSION@
Title: tdecachegrind
Version: @TDECACHEGRIND_VERSION@
Description: KDE Profiling Visualisation Tool
Keywords: Profiling, Performance Analysis, Visualisation, Development
Author: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
Maintained-by: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
Home-page: http://kcachegrind.sourceforge.net
Home-page: http://tdecachegrind.sourceforge.net
Platforms: Linux and other Unices
Copying-policy: GNU Public License
End

@ -1,13 +1,13 @@
Summary: KDE Profiling Visualisation Tool
Name: kcachegrind
Version: @KCACHEGRIND_VERSION@
Name: tdecachegrind
Version: @TDECACHEGRIND_VERSION@
Release: 1
Copyright: GPL
Group: Development/Tools
Vendor: (none)
URL: http://kcachegrind.sourceforge.net
URL: http://tdecachegrind.sourceforge.net
Packager: Josef Weidendorfer <Josef.Weidendorfer@gmx.de>
Source: kcachegrind-@KCACHEGRIND_VERSION@.tar.gz
Source: tdecachegrind-@TDECACHEGRIND_VERSION@.tar.gz
BuildRoot: /var/tmp/build
%description
@ -42,14 +42,14 @@ make -j$numprocs
make install-strip DESTDIR=$RPM_BUILD_ROOT
cd $RPM_BUILD_ROOT
find . -type d | sed '1,2d;s,^\.,\%attr(-\,root\,root) \%dir ,' > $RPM_BUILD_DIR/file.list.kcachegrind
find . -type f | sed 's,^\.,\%attr(-\,root\,root) ,' >> $RPM_BUILD_DIR/file.list.kcachegrind
find . -type l | sed 's,^\.,\%attr(-\,root\,root) ,' >> $RPM_BUILD_DIR/file.list.kcachegrind
find . -type d | sed '1,2d;s,^\.,\%attr(-\,root\,root) \%dir ,' > $RPM_BUILD_DIR/file.list.tdecachegrind
find . -type f | sed 's,^\.,\%attr(-\,root\,root) ,' >> $RPM_BUILD_DIR/file.list.tdecachegrind
find . -type l | sed 's,^\.,\%attr(-\,root\,root) ,' >> $RPM_BUILD_DIR/file.list.tdecachegrind
%clean
rm -rf $RPM_BUILD_ROOT/*
rm -rf $RPM_BUILD_DIR/kcachegrind
rm -rf ../file.list.kcachegrind
rm -rf $RPM_BUILD_DIR/tdecachegrind
rm -rf ../file.list.tdecachegrind
%files -f ../file.list.kcachegrind
%files -f ../file.list.tdecachegrind

@ -2,7 +2,7 @@
#---------------------------------------------------------------------------
# General configuration options
#---------------------------------------------------------------------------
PROJECT_NAME = kcachegrind
PROJECT_NAME = tdecachegrind
PROJECT_NUMBER =
OUTPUT_DIRECTORY =
OUTPUT_LANGUAGE = English

@ -1,6 +1,6 @@
bin_PROGRAMS = kcachegrind
bin_PROGRAMS = tdecachegrind
kcachegrind_SOURCES = \
tdecachegrind_SOURCES = \
functionselectionbase.ui \
stackselectionbase.ui \
partselectionbase.ui \
@ -19,24 +19,24 @@ kcachegrind_SOURCES = \
costlistitem.cpp partlistitem.cpp functionitem.cpp \
instritem.cpp stackitem.cpp callgraphview.cpp
kcachegrind_COMPILE_FIRST = ../version.h
tdecachegrind_COMPILE_FIRST = ../version.h
kcachegrind_LDADD = $(LIB_KIO)
tdecachegrind_LDADD = $(LIB_KIO)
KDE_ICON = AUTO
xdg_apps_DATA = kcachegrind.desktop
xdg_apps_DATA = tdecachegrind.desktop
mimeapplicationdir = $(kde_mimedir)/application
mimeapplication_DATA = x-kcachegrind.desktop
mimeapplication_DATA = x-tdecachegrind.desktop
EXTRA_DIST = \
kcachegrind.desktop \
x-kcachegrind.desktop \
hi32-app-kcachegrind.png \
hi48-app-kcachegrind.png \
tdecachegrind.desktop \
x-tdecachegrind.desktop \
hi32-app-tdecachegrind.png \
hi48-app-tdecachegrind.png \
Doxyfile \
kcachegrindui.rc
tdecachegrindui.rc
# set the include path for X, qt and KDE
INCLUDES= $(all_includes)
@ -44,19 +44,19 @@ INCLUDES= $(all_includes)
METASOURCES = AUTO
# the library search path.
kcachegrind_LDFLAGS = $(all_libraries) $(KDE_RPATH) $(LIB_QT) -lDCOP $(LIB_TDECORE) $(LIB_TDEUI) -ltdefx $(LIB_KIO) -lktexteditor
tdecachegrind_LDFLAGS = $(all_libraries) $(KDE_RPATH) $(LIB_QT) -lDCOP $(LIB_TDECORE) $(LIB_TDEUI) -ltdefx $(LIB_KIO) -lktexteditor
rcdir = $(kde_datadir)/kcachegrind
rc_DATA = kcachegrindui.rc
rcdir = $(kde_datadir)/tdecachegrind
rc_DATA = tdecachegrindui.rc
tipdir = $(kde_datadir)/kcachegrind
tipdir = $(kde_datadir)/tdecachegrind
tip_DATA = tips
messages: rc.cpp
$(PREPARETIPS) > tips.txt
LIST=`find . -name \*.h -o -name \*.cpp -o -name \*.txt`; \
if test -n "$$LIST"; then \
$(XGETTEXT) $$LIST -o $(podir)/kcachegrind.pot; \
$(XGETTEXT) $$LIST -o $(podir)/tdecachegrind.pot; \
fi
rm -f tips.txt

@ -1,10 +1,10 @@
# KDE Config File
[Desktop Entry]
Type=Application
Exec=kcachegrind -caption "%c" %i %m %u
MimeType=application/x-kcachegrind;
Icon=kcachegrind
DocPath=kcachegrind/index.html
Exec=tdecachegrind -caption "%c" %i %m %u
MimeType=application/x-tdecachegrind;
Icon=tdecachegrind
DocPath=tdecachegrind/index.html
Terminal=false
Name=KCachegrind
Name[hi]=के-केश-ग्रिंड

@ -1,5 +1,5 @@
<!DOCTYPE kpartgui>
<kpartgui name="kcachegrind" version="4">
<kpartgui name="tdecachegrind" version="4">
<MenuBar>
<Menu name="file"><text>&amp;File</text>
<Action name="file_add" append="open_merge"/>

@ -20,7 +20,7 @@
* KCachegrind startup
*/
// for KCACHEGRIND_VERSION
// for TDECACHEGRIND_VERSION
#include "../version.h"
#include <tqfile.h>
@ -42,13 +42,13 @@ static KCmdLineOptions options[] =
int main( int argc, char ** argv )
{
KAboutData aboutData("kcachegrind",
KAboutData aboutData("tdecachegrind",
I18N_NOOP("KCachegrind"),
KCACHEGRIND_VERSION,
TDECACHEGRIND_VERSION,
I18N_NOOP("KDE Frontend for Cachegrind"),
KAboutData::License_GPL,
I18N_NOOP("(C) 2002, 2003, 2004"), 0,
"http://kcachegrind.sf.net");
"http://tdecachegrind.sf.net");
aboutData.addAuthor("Josef Weidendorfer",
I18N_NOOP("Author/Maintainer"),
"Josef.Weidendorfer@gmx.de");

@ -37,8 +37,8 @@ Comment[tg]=Дампи профилкунии Cachegrind/Callgrind
Comment[uk]=Звалювання профілювання Cachegrind/Callgrind
Comment[zh_CN]=Cachegrind/Callgrind 配置文件转存
Comment[zh_TW]=Cachegrind/Callgrind 分析資料傾印
DefaultApp=kcachegrind
Icon=kcachegrind
DefaultApp=tdecachegrind
Icon=tdecachegrind
Type=MimeType
MimeType=application/x-kcachegrind
MimeType=application/x-tdecachegrind
Patterns=cachegrind.out*;callgrind.out*

@ -1,3 +1,3 @@
kcachegrindicondir = $(kde_datadir)/kcachegrind/icons
kcachegrindicon_ICON = AUTO
tdecachegrindicondir = $(kde_datadir)/tdecachegrind/icons
tdecachegrindicon_ICON = AUTO
SUBDIRS = hicolor

@ -1,2 +1,2 @@
kcachegrindicondir = $(kde_datadir)/kcachegrind/icons
kcachegrindicon_ICON = AUTO
tdecachegrindicondir = $(kde_datadir)/tdecachegrind/icons
tdecachegrindicon_ICON = AUTO

@ -1 +1 @@
#define KCACHEGRIND_VERSION "@KCACHEGRIND_VERSION@"
#define TDECACHEGRIND_VERSION "@TDECACHEGRIND_VERSION@"

Loading…
Cancel
Save