Browsing Cherokee translation

193.

<p>...that you can configure the maximum number of items
for all function lists in KCachegrind? Limiting the number
of items is done to get a fast reacting GUI. The last item in
the list will show you the number of skipped functions, together
with a cost condition for these skipped functions.</p>
<p>To activate a function with small costs, search for it and select
it in the flat profile. Selecting functions with small cost will
temporarily add them to the flat profile list.</p>

194.

<p>...that the Coverage tab - in contrast to the Call Lists tab -
shows <em>all</em> functions that are calling the selected function
(upper part) / are called by the selected function (bottom part),
no matter how many function are between them on the stack?</p>
<p>Examples:</p>
<p>An entry in the upper list for function foo1() with a value of 50%
with function bar() selected means that 50% of all the cost of function
bar() happened while called from function foo1().</p>
<p>An entry in the bottom list for function foo2() with a value of 50%
with function bar() selected means that 50% of all the cost of function
bar() happened while calling foo2() from bar().</p>

195.

<p>...that waiting for the tool tip inside of a tree map
shows the list of names of the nested rectangles the mouse
pointer is over?</p>
<p>Items from this list can be selected by pressing the right
mouse button.</p>

196.

<p>...that you can constrain the cost counts shown to only a
few parts of the whole trace by selecting these parts in the
"Trace Selection" Dockable?</p>
<p>To generate multiple parts in a profiling run with
cachegrind, use e.g. option --cachedumps=xxx for parts
of a length of xxx basic blocks (A basic block is a run
of not-branching assembler statements inside of your program
code).</p>