Browsing Turkish translation

21.

Context lines in annotations:

45.

While In

108.

Top Cost Call Stack

109.

<b>The Top Cost Call Stack</b><p>This is a purely fictional 'most probable' call stack. It is built up by starting with the current selected function and adds the callers/callees with highest cost at the top and to bottom.</p><p>The <b>Cost</b> and <b>Calls</b> columns show the cost used for all calls from the function in the line above.</p>

111.

<b>Profile Dumps</b><p>This dockable shows in the top part the list of loadable profile dumps in all subdirectories of: <ul><li>current working directory of KCachegrind, i.e. where it was started from, and </li><li>the default profile dump directory given in the configuration.</li></ul> The list is sorted according to the target command profiled in the corresponding dump.</p><p>On selecting a profile dump, information for it is shown in the bottom area of the dockable: <ul><li><b>Options</b> allows you to view the profiled command and profile options of this dump. By changing any item, a new (yet unexisting) profile template is created. Press <b>Run Profile</b> to start a profile run with these options in the background. </li><li><b>Info</b> gives detailed info on the selected dump like event cost summary and properties of the simulated cache. </li><li><b>State</b> is only available for current happening profiles runs. Press <b>Update</b> to see different counters of the run, and a stack trace of the current position in the program profiled. Check the <b>Every</b> option to let KCachegrind regularly poll these data. Check the <b>Sync</b> option to let the dockable activate the top function in the current loaded dump.</li></ul></p>

132.

<b>Force Dump</b><p>This forces a dump for a Callgrind profile run in the current directory. This action is checked while KCachegrind looks for the dump. If the dump is finished, it automatically reloads the current trace. If this is the one from the running Callgrind, the new created trace part will be loaded, too.</p><p>Force dump creates a file 'callgrind.cmd', and checks every second for its existence. A running Callgrind will detect this file, dump a trace part, and delete 'callgrind.cmd'. The deletion is detected by KCachegrind, and it does a Reload. If there is <em>no</em> Callgrind running, press 'Force Dump' again to cancel the dump request. This deletes 'callgrind.cmd' itself and stops polling for a new dump.</p><p>Note: A Callgrind run <em>only</em> detects existence of 'callgrind.cmd' when actively running a few milliseconds, i.e. <em>not</em> sleeping. Tip: For a profiled GUI program, you can awake Callgrind e.g. by resizing a window of the program.</p>

134.

Show/Hide the Parts Overview Dockable

136.

Show/Hide the Call Stack Dockable

138.

Show/Hide the Function Profile Dockable

139.

Show/Hide the Profile Dumps Dockable