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.
Timothy Pearson
13 years ago