Translation by Artem Sereda with my minor changes

[kde-ru.git] / docmessages / kdesdk / kcachegrind.po

# KDE3 - kcachegrind.pot Russian translation.
#
# Nick Shaforostoff <shafff@ukr.net>, 2003-2005, 2006.
msgid ""
msgstr ""
"Project-Id-Version: kcachegrind\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2008-07-24 03:25+0000\n"
"PO-Revision-Date: 2006-05-18 18:18+0300\n"
"Last-Translator: Nick Shaforostoff <shafff@ukr.net>\n"
"Language-Team: Russian <kde-russian@lists.kde.ru>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: KBabel 1.11.2\n"
"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%"
"10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n"

#. Tag: title
#: index.docbook:20
#, no-c-format
msgid "The &kcachegrind; Handbook"
msgstr "Руководство &kcachegrind;"

#. Tag: author
#: index.docbook:23
#, no-c-format
msgid "<firstname>Josef</firstname> <surname>Weidendorfer</surname>"
msgstr "<firstname>Josef</firstname> <surname>Weidendorfer</surname>"

#. Tag: email
#: index.docbook:27
#, no-c-format
msgid "Josef.Weidendorfer@gmx.de"
msgstr "Josef.Weidendorfer@gmx.de"

#. Tag: trans_comment
#: index.docbook:31
#, no-c-format
msgid "ROLES_OF_TRANSLATORS"
msgstr ""

#. Tag: holder
#: index.docbook:37
#, no-c-format
msgid "&Josef.Weidendorfer;"
msgstr "&Josef.Weidendorfer;"

#. Tag: para
#: index.docbook:45
#, no-c-format
msgid ""
"&kcachegrind; is a profile data visualization tool, written using the &kde; "
"environment."
msgstr ""

#. Tag: keyword
#: index.docbook:51
#, no-c-format
msgid "<keyword>KDE</keyword>"
msgstr "<keyword>KDE</keyword>"

#. Tag: keyword
#: index.docbook:52
#, no-c-format
msgid "kdesdk"
msgstr "kdesdk"

#. Tag: keyword
#: index.docbook:53
#, no-c-format
msgid "Cachegrind"
msgstr "Cachegrind"

#. Tag: keyword
#: index.docbook:54
#, no-c-format
msgid "Callgrind"
msgstr "Callgrind"

#. Tag: keyword
#: index.docbook:55
#, no-c-format
msgid "Valgrind"
msgstr "Valgrind"

#. Tag: keyword
#: index.docbook:56
#, no-c-format
msgid "<keyword>Profiling</keyword>"
msgstr "<keyword>Профилирование</keyword>"

#. Tag: title
#: index.docbook:63
#, no-c-format
msgid "Introduction"
msgstr "Введение"

#. Tag: para
#: index.docbook:65
#, no-c-format
msgid ""
"&kappname; is a browser for data produced by profiling tools. This chapter "
"explains what profiling is for, how it is done, and gives some examples of "
"profiling tools available."
msgstr ""

#. Tag: title
#: index.docbook:72
#, no-c-format
msgid "<title>Profiling</title>"
msgstr ""

#. Tag: para
#: index.docbook:74
#, no-c-format
msgid ""
"When developing a program, one of the last steps often involves performance "
"optimizations. As it makes no sense to optimize functions rarely used, "
"because that would be a waste of time, one needs to know in which part of a "
"program most of the time is spent."
msgstr ""
"Завершающим шагом разработки качественного программного обеспечения обычно "
"является его оптимизация, т.е. увеличение производительности. И, чтобы не "
"терять время на улучшение редко используемых функций, вы можете использовать "
"профилирование."

#. Tag: para
#: index.docbook:82
#, no-c-format
msgid ""
"For sequential code, collecting statistical data of the programs runtime "
"characteristic like time numbers spent in functions and code lines usually "
"is enough. This is called Profiling. The program is run under control of a "
"profiling tool, which gives the summary of an execution run at the end. In "
"contrast, for parallel code, performance problems typically are caused when "
"one processor is waiting for data from another. As this waiting time usually "
"cannot easily attributed, here it is better to generate timestamped event "
"traces. &kcachegrind; cannot visualize this kind of data."
msgstr ""

#. Tag: para
#: index.docbook:90
#, no-c-format
msgid ""
"After analyzing the produced profile data, it should be easy to see the hot "
"spots and bottlenecks of the code: for example, assumptions about call "
"counts can be checked, and identified code regions can be optimized. "
"Afterwards, the success of the optimization should be verified with another "
"profile run."
msgstr ""

#. Tag: title
#: index.docbook:99
#, no-c-format
msgid "Profiling Methods"
msgstr "Методы профилирования"

#. Tag: para
#: index.docbook:101
#, no-c-format
msgid ""
"To exactly measure the time passed or record the events happening during the "
"execution of a code region (&eg; a function), additional measurement code "
"needs to be inserted before and after the given region. This code reads the "
"time, or a global event count, and calculates differences. Thus, the "
"original code has to be changed before execution. This is called "
"instrumentation. Instrumentation can be done by the programmer itself, the "
"compiler, or by the runtime system. As interesting regions usually are "
"nested, the overhead of measurement always influences the measurement "
"itself. Thus, instrumentation should be done selectively and results have to "
"be interpreted with care. Of course, this makes performance analysis by "
"exact measurement a very complex process."
msgstr ""

#. Tag: para
#: index.docbook:103
#, no-c-format
msgid ""
"Exact measurement is possible because of hardware counters (including "
"counters incrementing on a time tick) provided in modern processors, which "
"are incremented whenever an event is happening. As we want to attribute "
"events to code regions, without the counters, we would have to handle every "
"event by incrementing a counter for the current code region ourself. Doing "
"this in software is, of course, not possible; but, on the assumption that "
"the event distribution over source code is similar when looking only at "
"every n-th event instead of every event, a measurement method whose overhead "
"is tunable has been developed: it is called Sampling. Time Based Sampling "
"(TBS) uses a timer to regularly look at the program counter to create a "
"histogram over the program code. Event Based Sampling (EBS) exploits the "
"hardware counters of modern processors, and uses a mode where an interrupt "
"handler is called on counter underflow to generate a histogram of the "
"corresponding event distribution: in the handler, the event counter is "
"always reinitialized to the 'n' of the sampling method. The advantage of "
"sampling is that the code does not have to be changed, but it is still a "
"compromise: the above assumption will be more correct if n is small, but the "
"smaller the n, the higher the overhead of the interrupt handler."
msgstr ""

#. Tag: para
#: index.docbook:106
#, no-c-format
msgid ""
"Another measurement method is to simulate things happening in the computer "
"system when executing a given code, &ie; execution driven simulation. The "
"simulation is always derived from a more or less accurate machine model; "
"however, with very detailed machine models, giving very close approximations "
"to reality, the simulation time can be unacceptably high in practice. The "
"advantage of simulation is that arbitrarily complex measurement/simulation "
"code can be inserted in a given code without perturbing results. Doing this "
"directly before execution (called runtime instrumentation), using the "
"original binary, is very comfortable for the user: no re-compilation is "
"necessary. Simulation becomes usable when simulating only parts of a machine "
"with a simple model; another advantage is that the results produced by "
"simple models are often easier to understand: often, the problem with real "
"hardware is that results include overlapping effects from different parts of "
"the machine."
msgstr ""

#. Tag: title
#: index.docbook:110
#, no-c-format
msgid "Profiling Tools"
msgstr "Средства профилирования"

#. Tag: para
#: index.docbook:112
#, no-c-format
msgid ""
"Most known is the GCC profiling tool <application>gprof</application>: One "
"needs to compile the program with option <option>-pg</option>; running the "
"program generates a file <filename>gmon.out</filename>, which can be "
"transformed into human-readable form with <command>gprof</command>. One "
"disadvantage is the needed re-compilation step to prepare the executable, "
"which has to be statically linked. The method used here is compiler-"
"generated instrumention - which measures call arcs happening among functions "
"and corresponding call counts - in conjunction with TBS - which gives a "
"histogram of time distribution over the code. Using both pieces of "
"information, it is possible to heuristically calculate inclusive time of "
"functions, &ie; time spent in a function together with all functions called "
"from it."
msgstr ""
"Наиболее известным средством профилирования является <application>gprof</"
"application> (входит в комплект GCC). Откомпилируйте программу с ключом "
"<option>-pg</option>; дальнейшее её выполнение приведёт к созданию файла "
"<filename>gmon.out</filename>, который можно преобразовать в приемлемый для "
"чтения вид командой <command>gprof</command>. В минусы такого способа "
"следует отнести требуемый шаг компиляции приложения, которое должно быть "
"скомпоновано статически. ́При компиляции в код вставляются специальные "
"инструкции для замера времени выполнения цепей вызовов в функциях и подсчёта "
"их количества, что в сочетании с временно́й дискретизацией позволяет получить "
"гистограмму распределе используемого времени по участкам кодаodТаким "
"образом, становится возможным эвристическое вычисление общего времени "
"выполнения функций, т.е. время на выполнение инструкций самой функции и всех "
"функций, вызываемых из неё it."

#. Tag: para
#: index.docbook:122
#, no-c-format
msgid ""
"For exact measurement of events happening, libraries exist with functions "
"able to read out hardware performance counters. Most known here is the "
"PerfCtr patch for &Linux;, and the architecture independent libraries PAPI "
"and PCL. Still, exact measurement needs instrumentation of code, as stated "
"above. Either one uses the libraries itself or uses automatic "
"instrumentation systems like ADAPTOR (for FORTRAN source instrumentation) or "
"DynaProf (code injection via DynInst)."
msgstr ""

#. Tag: para
#: index.docbook:124
#, no-c-format
msgid "&oprofile; is a system-wide profiling tool for &Linux; using Sampling."
msgstr ""

#. Tag: para
#: index.docbook:126
#, no-c-format
msgid ""
"In many aspects, a comfortable way of Profiling is using &cachegrind; or "
"&callgrind;, which are simulators using the runtime instrumentation "
"framework &valgrind;. Because there is no need to access hardware counters "
"(often difficult with today's &Linux; installations), and binaries to be "
"profiled can be left unmodified, it is a good alternative to other profiling "
"tools. The disadvantage of simulation - slowdown - can be reduced by doing "
"the simulation on only the interesting program parts, and perhaps only on a "
"few iterations of a loop. Without measurement/simulation instrumentation, "
"&valgrind;'s usage only has a slowdown factor in the range of 3 to 5. Also, "
"when only the call graph and call counts are of interest, the cache "
"simulator can be switched off."
msgstr ""

#. Tag: para
#: index.docbook:137
#, no-c-format
msgid ""
"Cache simulation is the first step in approximating real times; as ,on "
"modern systems, runtime is very sensitive to the exploitation of so called "
"caches (small and fast buffers which accelerate repeated accesses to the "
"same main memory cells.) &cachegrind; does cache simulation by catching "
"memory accesses. The data produced includes the number of instruction/data "
"memory accesses and 1st/2nd level cache misses, and relates it to source "
"lines and functions of the run program. By combining these miss counts, "
"using miss latencies from typical processors, an estimation of spent time "
"can be given."
msgstr ""
"Первым шагом в увеличении производительности является симулирование "
"кэширования. Оно заключается в перехватывании всех обращений к памяти без "
"перекомпиляции программы; при этом можно использовать динамически "
"подключаемые библиотеки и модули. Трассировка определяет число инструкций/"
"обращений к данным, уровень недостатка кэша (1-ой или 2-ой) и устанавливает "
"соответствующее место в исходных кодах. Таким образом,, учитывая латентность "
"из-за недостатка объёма кэша среднего процессора, можно предположительно "
"подсчитать затраты времени."

#. Tag: para
#: index.docbook:150
#, no-c-format
msgid ""
"&callgrind; is an extension of &cachegrind; that builds up the call graph of "
"a program on-the-fly, &ie; how the functions call each other and how many "
"events happen while running a function. Also, the profile data to be "
"collected can separated by threads and call chain contexts. It can provide "
"profiling data on an instruction level to allow for annotation of "
"disassembled code."
msgstr ""
"&callgrind; - это расширение &cachegrind;, строящее график вызовов программы "
"\"на лету\". Он говорит о том, как функции вызывают одна другую и как много "
"событий происходит во время выполнения функции. Собираемые данные "
"профилирования могут быть разделены на потоки и контексты цепочки вызовов. "
"Данные профилирования могут быть предоставлены на уровне инструкций "
"ассемблера."

#. Tag: title
#: index.docbook:161
#, no-c-format
msgid "Visualization"
msgstr "Визуализация"

#. Tag: para
#: index.docbook:163
#, no-c-format
msgid ""
"Profiling tools typically produce a large amount of data. The wish to easily "
"browse down and up the call graph, together with fast switching of the "
"sorting mode of functions and display of different event types, motivates a "
"&GUI; application to accomplish this task."
msgstr ""

#. Tag: para
#: index.docbook:168
#, no-c-format
msgid ""
"&kappname; is an visualization for profile data fulfilling these wishes. "
"Despite being programmed first with browsing the data from &cachegrind; and "
"&calltree; in mind, there are converters available to be able to display "
"profile data produced by other tools. In the appendix, a description of the "
"&cachegrind;/&callgrind; file format is given."
msgstr ""

#. Tag: para
#: index.docbook:172
#, no-c-format
msgid ""
"Besides a list of functions sorted according exclusive or inclusive cost "
"metrics, and optionally grouped by source file, shared library or C++ class, "
"&kappname; features various visualization views for a selected function, "
"namely"
msgstr ""

#. Tag: para
#: index.docbook:177
#, no-c-format
msgid ""
"a call-graph view, which shows a section of the call graph around the "
"selected function,"
msgstr ""

#. Tag: para
#: index.docbook:179
#, no-c-format
msgid ""
"a tree-map view, which allows nested-call relations to be visualized, "
"together with inclusive cost metric for fast visual detection of problematic "
"functions,"
msgstr ""

#. Tag: para
#: index.docbook:181
#, no-c-format
msgid ""
"source code and disassembler annotation views, allowing to see details of "
"cost related to source lines and assembler instructions."
msgstr ""

#. Tag: title
#: index.docbook:190
#, no-c-format
msgid "Using &kcachegrind;"
msgstr "Использование &kcachegrind;"

#. Tag: title
#: index.docbook:193
#, no-c-format
msgid "Generate Data to Visualize"
msgstr ""

#. Tag: para
#: index.docbook:195
#, no-c-format
msgid ""
"First, one wants to generate performance data by measuring aspects of the "
"runtime characteristics of an application, using a profiling tool. "
"&kcachegrind; 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 with these tools, the next section "
"provides short quickstart tutorials to get you started."
msgstr ""

#. Tag: title
#: index.docbook:204
#, no-c-format
msgid "&callgrind;"
msgstr "&callgrind;"

#. Tag: para
#: index.docbook:206
#, no-c-format
msgid ""
"&callgrind; is available from <ulink url=\"http://kcachegrind.sf.net\"> "
"http://kcachegrind.sf.net</ulink>. Note that it previously was called "
"&calltree;, but that name was misleading."
msgstr ""

#. Tag: para
#: index.docbook:213
#, no-c-format
msgid ""
"Most common use is to prefix the command line to start your application with "
"<application>callgrind</application>, like in "
"<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;."
msgstr ""

#. Tag: para
#: index.docbook:223
#, no-c-format
msgid ""
"More advanced use is to dump out profile data whenever a given function of "
"your application is called. E.g. for <command>konqueror</command>, to see "
"profile data only for rendering a web page, you could decide to dump the "
"data whenever you select the menu item View/Reload. This corresponds to a "
"call to <symbol>KonqMainWindow::slotReload</symbol>. Use "
"<blockquote><para><command> callgrind --dump-before=KonqMainWindow::"
"slotReload konqueror </command></para></blockquote> 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 be seen in the Parts "
"Overview and Parts list."
msgstr ""

#. Tag: title
#: index.docbook:244
#, no-c-format
msgid "&oprofile;"
msgstr ""

#. Tag: para
#: index.docbook:246
#, no-c-format
msgid ""
"&oprofile; is available from <ulink url=\"http://oprofile.sf.net\"> http://"
"oprofile.sf.net</ulink>. Follow the installation instructions on the web "
"site; but, before you do, check if your distribution does not already "
"provide it as package (like &SuSE;)."
msgstr ""

#. Tag: para
#: index.docbook:253
#, no-c-format
msgid ""
"System-wide profiling is only permitted to the root user, as all actions on "
"the system can be observed; therefore, the following has to be done as root. "
"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 folder "
"<filename>/var/lib/oprofile/samples/</filename>. To be able to visualize the "
"data in &kcachegrind;, 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."
msgstr ""

#. Tag: title
#: index.docbook:273
#, no-c-format
msgid "User Interface Basics"
msgstr ""

#. Tag: para
#: index.docbook:275
#, no-c-format
msgid ""
"When starting &kcachegrind; with a profile data file as argument, or after "
"loading one with File/Open, you will see a navigation panel 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."
msgstr ""

#. Tag: para
#: index.docbook:282
#, no-c-format
msgid ""
"At first start, this area will be divided into a top and a bottom part, each "
"with different visualizations selectable by tabs. To move visualization "
"views, use the context menu of the tabs, and adjust the splitters between "
"visualizations. To quickly switch between different visualization layouts, "
"use View/Layouts/Duplicate, change the layout and switch between layouts "
"with View/Layout/Next (or, even better, use the corresponding keyboard "
"shortcuts)."
msgstr ""

#. Tag: para
#: index.docbook:292
#, no-c-format
msgid ""
"The active event type is important for visualization: for &callgrind;, this "
"is, for example, Cache Misses or Cycle Estimation; for &oprofile;, this is "
"\"Timer\" in the simplest case. You can change the event type via a combobox "
"in the toolbar or in the Event Type view. A first overview of the runtime "
"characteristics should be given when you select function <symbol>main</"
"symbol> in the left list, and look at the call graph visualization; there, "
"you see calls happening in your program. Note that the call graph view only "
"shows functions with high event count. By double-clicking a function in the "
"graph, it will change to show the called functions around the selected one."
msgstr ""

#. Tag: para
#: index.docbook:298
#, no-c-format
msgid ""
"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>. Also, every widget in "
"&kcachegrind; has <quote>What's this</quote> help."
msgstr ""
"Для более углублённого изучения интерфейса программы обратитесь к разделу "
"документации web-сайта <ulink url=\"http://kcachegrind.sf.net\"> http://"
"kcachegrind.sf.net</ulink>.Кроме того, у всех графических элементов "
"&kcachegrind; есть справка <quote>Что это?</quote>."

#. Tag: title
#: index.docbook:311
#, no-c-format
msgid "Basic Concepts"
msgstr ""

#. Tag: para
#: index.docbook:313
#, no-c-format
msgid ""
"This chapter explains some concepts of the &kcachegrind;, and introduces "
"terms used in the interface."
msgstr ""

#. Tag: title
#: index.docbook:318
#, no-c-format
msgid "The Data Model for Profile Data"
msgstr ""

#. Tag: title
#: index.docbook:321
#, no-c-format
msgid "Cost Entities"
msgstr ""

#. Tag: para
#: index.docbook:323
#, no-c-format
msgid ""
"Cost counts of event types (like L2 Misses) are attributed to cost entities, "
"which are items with relationship to source code or data structures of a "
"given program. Cost entities not only can be simple code or data positions, "
"but also position tuples. For example, a call has a source and a target, or "
"a data address can have a data type and an code position where its "
"allocation happened."
msgstr ""

#. Tag: para
#: index.docbook:327
#, no-c-format
msgid ""
"The cost entities known to &kcachegrind; are given in the following. Simple "
"Positions: <itemizedlist> <listitem><para> Instruction. An assembler "
"instruction at a specified address. </para></listitem> <listitem><para> "
"Source Line of a Function. All instructions that the compiler (via debug "
"information) maps to a given source line specified by source file name and "
"line number, and which are executed in the context of some function. The "
"latter is needed because a source line inside of an inlined function can "
"appear in the context of multiple functions. Instructions without any "
"mapping to an actual source line are mapped to line number 0 in file \"???"
"\". </para></listitem> <listitem><para> Function. All source lines of a "
"given function make up the function itself. A function is specified by its "
"name and its location in some binary object if available. The latter is "
"needed because binary objects of a single program each can hold functions "
"with the same name (these can be accessed &eg; with dlopen/dlsym; the "
"runtime linker resolves functions in a given search order of binary objects "
"used). If a profiling tool cannot detect the symbol name of a function, &eg; "
"because debug information is not available, either the address of the first "
"executed instruction typically is used, or \"???\". </para></listitem> "
"<listitem><para> Binary Object. All functions whose code is inside the range "
"of a given binary object, either the main executable or a shared library. </"
"para></listitem> <listitem><para> Source File. All functions whose first "
"instruction is mapped to a line of the given source file. </para></listitem> "
"<listitem><para> Class. Symbol names of functions typically are "
"hierarchically ordered in name spaces, &eg; C++ namespaces, or classes of "
"object oriented languages; thus, a class can hold functions of the class or "
"embedded classes itself. </para></listitem> <listitem><para> Profile Part. "
"Some time section of a profile run, with a given thread ID, process ID, and "
"command line executed. </para></listitem> </itemizedlist> As can be seen "
"from the list, a set of cost entities often defines another cost entity; "
"thus, there is a inclusion hierarchy of cost entities which should be "
"obvious from the description above."
msgstr ""

#. Tag: para
#: index.docbook:363
#, no-c-format
msgid ""
"Positions tuples: <itemizedlist> <listitem><para> Call from instruction "
"address to target function. </para></listitem> <listitem><para> Call from "
"source line to target function. </para></listitem> <listitem><para> Call "
"from source function to target function. </para></listitem> <listitem><para> "
"(Un)conditional Jump from source to target instruction. </para></listitem> "
"<listitem><para> (Un)conditional Jump from source to target line. </para></"
"listitem> </itemizedlist> Jumps between functions are not allowed, as this "
"makes no sense in a call graph; thus, constructs like exception handling and "
"long jumps in C have to be translated to popping the call stack as needed."
msgstr ""

#. Tag: title
#: index.docbook:391 index.docbook:541
#, no-c-format
msgid "Event Types"
msgstr ""

#. Tag: para
#: index.docbook:393
#, no-c-format
msgid ""
"Arbitrary event types can be specified in the profile data by giving them a "
"name. Their cost related to a cost entity is a 64-bit integer."
msgstr ""

#. Tag: para
#: index.docbook:396
#, no-c-format
msgid ""
"Event types whose costs are specified in a profile data file are called real "
"events. Additionally, one can specify formulas for event types calculated "
"from real events, which are called inherited events."
msgstr ""

#. Tag: title
#: index.docbook:404
#, no-c-format
msgid "Visualization State"
msgstr ""

#. Tag: para
#: index.docbook:406
#, no-c-format
msgid ""
"The Visualization state of a &kcachegrind; window includes: <itemizedlist> "
"<listitem><para> the primary and secondary event type chosen for display, </"
"para></listitem> <listitem><para> the function grouping (used in the "
"Function Profile list and entity coloring), </para></listitem> "
"<listitem><para> the profile parts whose costs are to be included in "
"visualization, </para></listitem> <listitem><para> an active cost entity "
"(&eg; a function selected from the function profile dockable), </para></"
"listitem> <listitem><para> a selected cost entity. </para></listitem> </"
"itemizedlist> This state influences visualizations."
msgstr ""

#. Tag: para
#: index.docbook:428
#, no-c-format
msgid ""
"Visualizations always are shown for one, the active, cost entity. When a "
"given visualization is not appropriate for a cost entity, it is disabled "
"(&eg; when selecting an &ELF; object in the group list by double-clicking, "
"source annotation for an &ELF; object make no sense)."
msgstr ""

#. Tag: para
#: index.docbook:431
#, no-c-format
msgid ""
"For example, for an active function, the callee list shows all the functions "
"called from the active one: one can select one of these functions without "
"making it active; also, if the call-graph is shown nearside, it will "
"automatically select the same function."
msgstr ""

#. Tag: title
#: index.docbook:438
#, no-c-format
msgid "Parts of the &GUI;"
msgstr ""

#. Tag: title
#: index.docbook:441 index.docbook:496
#, no-c-format
msgid "Sidedocks"
msgstr ""

#. Tag: para
#: index.docbook:442
#, no-c-format
msgid ""
"Sidedocks (Dockables) are side windows which can be placed at any border of "
"an &kcachegrind; window. They always contain a list of cost entities sorted "
"in some manner."
msgstr ""

#. Tag: para
#: index.docbook:445
#, no-c-format
msgid ""
"Function Profile. The Function Profile is a list of functions showing "
"inclusive and exclusive cost, call count, name and position of functions."
msgstr ""

#. Tag: para
#: index.docbook:449
#, no-c-format
msgid "<para>Parts Overview</para>"
msgstr ""

#. Tag: para
#: index.docbook:452
#, no-c-format
msgid "<para>Call Stack</para>"
msgstr ""

#. Tag: title
#: index.docbook:460
#, no-c-format
msgid "Visualization Area"
msgstr ""

#. Tag: para
#: index.docbook:461
#, no-c-format
msgid ""
"The visualization area, typically the right part of a &kcachegrind; main "
"window, is made up of one (default) or more Tab Views, either lined up "
"horizontally or vertically. Each tab view holds different visualization "
"views of only one cost entity at a time. The name of this entity is given at "
"the top of the tab view. If there are multiple tab views, only one is "
"active. The entity name in the active tab view is shown in bold and "
"determines the active cost entity of the &kcachegrind; window."
msgstr ""

#. Tag: title
#: index.docbook:467
#, no-c-format
msgid "Areas of a Tab View"
msgstr ""

#. Tag: para
#: index.docbook:468
#, no-c-format
msgid ""
"Each tab view can hold up to four view areas, namely Top, Right, Left, and "
"Bottom. Each area can hold multiple stacked visualization views. The visible "
"view of an area is selected by a tab bar. The tab bars of the top and right "
"area are at the top; the tab bars of the left and bottom area are at the "
"bottom. You can specify which kind of visualization should go into which "
"area by using the context menus of the tabs."
msgstr ""

#. Tag: title
#: index.docbook:474
#, no-c-format
msgid "Synchronized Visualization via Selected Entity in a Tab View"
msgstr ""

#. Tag: para
#: index.docbook:475
#, no-c-format
msgid ""
"Besides an active entity, each tab view has an selected entity. As most "
"visualization types show multiple entities with the active one somehow "
"centered, you can change the selected item by navigating inside a "
"visualization (by clicking with the mouse or using the keyboard). Typically, "
"selected items are shown in an highlighted state. By changing the selected "
"entity in one of the visualizations of a tab view, all other visualizations "
"in the tab view accordingly highlight the new selected entity."
msgstr ""

#. Tag: title
#: index.docbook:481
#, no-c-format
msgid "Synchronization between Tab Views"
msgstr ""

#. Tag: para
#: index.docbook:482
#, no-c-format
msgid ""
"If there are multiple tab views, a selection change in one tab view leads to "
"an activation change in the next (to right/to bottom) tab view. This kind of "
"linkage should, for example, allow for fast browsing in call graphs."
msgstr ""

#. Tag: title
#: index.docbook:488
#, no-c-format
msgid "Layouts"
msgstr ""

#. Tag: para
#: index.docbook:489
#, no-c-format
msgid ""
"The layout of all the tab views of a window can be saved (see menu item View/"
"Layout). After duplicating the current layout (Ctrl+Plus or menu) and "
"changing some sizes or moving a visualization view to another area of an tab "
"view, you can quickly switch between the old and the new layout via Ctrl"
"+Left/Right. The set of layouts will be stored between &kcachegrind; "
"sessions of the same profiled command. You can make the current set of "
"layouts as the default one for new &kcachegrind; sessions, or restore to the "
"default layout set."
msgstr ""

#. Tag: title
#: index.docbook:499
#, no-c-format
msgid "Flat Profile"
msgstr ""

#. Tag: para
#: index.docbook:500
#, no-c-format
msgid ""
"The flat profile contains a group list and a function list. The group list "
"contains all groups where cost is spent in, depending on the chosen group "
"type. The group list is hidden when grouping is switched off."
msgstr ""

#. Tag: para
#: index.docbook:503
#, no-c-format
msgid ""
"The function list contains the functions of the selected group (or all "
"functions if grouping is switched off), ordered by some column, &eg; "
"inclusive or self costs spent therein. There is a maximal number of "
"functions shown in the list, which is configurable in Settings/Configure "
"&kcachegrind;."
msgstr ""

#. Tag: title
#: index.docbook:509
#, no-c-format
msgid "<title>Parts Overview</title>"
msgstr ""

#. Tag: para
#: index.docbook:510
#, no-c-format
msgid ""
"In a profile run, multiple profile data files can be produced, which can be "
"loaded together into &kcachegrind;. The Parts Overview dockable shows these, "
"horizontally ordered according creation time; the rectangle sizes are "
"proportional to the cost spent in the parts. You can select one or several "
"parts to constrain the costs shown in the other &kcachegrind; views to these "
"parts only."
msgstr ""

#. Tag: para
#: index.docbook:513
#, no-c-format
msgid ""
"The parts are further subdivided: there is a partitioning and an inclusive "
"cost split mode:"
msgstr ""

#. Tag: para
#: index.docbook:516
#, no-c-format
msgid ""
"Partitioning: You see the partitioning into groups for a profile data part, "
"according to the group type selected. For example, if &ELF; object groups "
"are selected, you see colored rectangles for each used &ELF; object (shared "
"library or executable), sized according to the cost spent therein."
msgstr ""

#. Tag: para
#: index.docbook:519
#, no-c-format
msgid ""
"Inclusive Cost Split: A rectangle showing the inclusive cost of the current "
"active function in the part is shown. This, again, is split up to show "
"inclusive costs of its callees."
msgstr ""

#. Tag: title
#: index.docbook:527
#, no-c-format
msgid "<title>Call Stack</title>"
msgstr ""

#. Tag: para
#: index.docbook:528
#, no-c-format
msgid ""
"This is a purely fictional 'most probable' call stack. It is built up by "
"starting with the current active function and adds the callers/callees with "
"highest cost at the top and to bottom."
msgstr ""

#. Tag: para
#: index.docbook:531
#, no-c-format
msgid ""
"The 'Cost' and 'Calls' columns show the cost used for all calls from the "
"function in the line above."
msgstr ""

#. Tag: title
#: index.docbook:538
#, no-c-format
msgid "Visualizations"
msgstr ""

#. Tag: para
#: index.docbook:542
#, no-c-format
msgid ""
"This list shows all cost types available and the corresponding self and "
"inclusive cost of the current active function for that event type."
msgstr ""

#. Tag: para
#: index.docbook:545
#, no-c-format
msgid ""
"By choosing an event type from the list, you change the type of costs shown "
"all over &kcachegrind; to be the selected one."
msgstr ""

#. Tag: title
#: index.docbook:551
#, no-c-format
msgid "Call Lists"
msgstr ""

#. Tag: para
#: index.docbook:552
#, no-c-format
msgid ""
"These lists show calls to/from the current active function. With ''all' "
"callers/callees functions are meant which can be reached in caller/callee "
"direction, even when other functions are in between."
msgstr ""

#. Tag: para
#: index.docbook:555
#, no-c-format
msgid "Call list views include:"
msgstr ""

#. Tag: para
#: index.docbook:558
#, no-c-format
msgid "Direct Callers"
msgstr ""

#. Tag: para
#: index.docbook:561
#, no-c-format
msgid "Direct Callees"
msgstr ""

#. Tag: para
#: index.docbook:564
#, no-c-format
msgid "All Callers"
msgstr ""

#. Tag: para
#: index.docbook:567
#, no-c-format
msgid "All Callees"
msgstr ""

#. Tag: title
#: index.docbook:575
#, no-c-format
msgid "Maps"
msgstr ""

#. Tag: para
#: index.docbook:576
#, no-c-format
msgid ""
"A treemap visualization of the primary event type, up or down the call "
"hierarchy. Each colored rectangle represents a function; its size tries to "
"be proportional to the cost spent therein while the active function is "
"running (however, there are drawing constrains)."
msgstr ""

#. Tag: para
#: index.docbook:579
#, no-c-format
msgid ""
"For the Caller Map, the graph shows the nested hierarchy of all callers of "
"the current activated function; for the Callee Map, it shows the nested "
"hierarchy of all callees of the current activated function."
msgstr ""

#. Tag: para
#: index.docbook:582
#, no-c-format
msgid ""
"Appearance options can be found in the in the context menu. To get exact "
"size proportions, choose 'Hide incorrect borders'. As this mode can be very "
"time consuming, you may want to limit the maximum drawn nesting level "
"before. 'Best' determinates the split direction for children from the aspect "
"ratio of the parent. 'Always Best' decides on remaining space for each "
"sibling. 'Ignore Proportions' takes space for function name drawing before "
"drawing children. Note that size proportions can get heavily wrong."
msgstr ""

#. Tag: para
#: index.docbook:585
#, no-c-format
msgid ""
"Keyboard navigation is available with the left/right arrow keys for "
"traversing siblings, and up/down arrow keys to go a nesting level up/down. "
"'Return' activates the current item."
msgstr ""

#. Tag: title
#: index.docbook:591
#, no-c-format
msgid "Call Graph"
msgstr ""

#. Tag: para
#: index.docbook:592
#, no-c-format
msgid ""
"This view shows the call graph around the active function. The shown cost is "
"only the cost which is spent while the active function was actually running; "
"&ie; the cost shown for main() - if it's visible - should be the same as the "
"cost of the active function, as that is the part of inclusive cost of main() "
"spent while the active function was running."
msgstr ""

#. Tag: para
#: index.docbook:596
#, no-c-format
msgid ""
"For cycles, blue call arrows indicate that this is an artificial call added "
"for correct drawing which actually never happened."
msgstr ""

#. Tag: para
#: index.docbook:599
#, no-c-format
msgid ""
"If the graph is larger than the widget area, a bird's eye view is shown in "
"one edge. There are similar visualization options as for the Call Treemap; "
"the selected function is highlighted."
msgstr ""

#. Tag: title
#: index.docbook:605
#, no-c-format
msgid "Annotations"
msgstr ""

#. Tag: para
#: index.docbook:606
#, no-c-format
msgid ""
"The annotated source/assembler lists show the source lines/disassembled "
"instructions of the current active function together with (self) cost spent "
"while executing the code of a source line/instruction. If there was a call, "
"lines with details on the call are inserted into the source: the (inclusive) "
"cost spent inside of the call, the number of calls happening, and the call "
"destination."
msgstr ""

#. Tag: para
#: index.docbook:609
#, no-c-format
msgid "Select such a call information line to activate the call destination."
msgstr ""

#. Tag: title
#: index.docbook:619
#, no-c-format
msgid "Command Reference"
msgstr "Список команд"

#. Tag: title
#: index.docbook:622
#, no-c-format
msgid "The main &kcachegrind; window"
msgstr "Главное окно &kcachegrind;"

#. Tag: title
#: index.docbook:625
#, no-c-format
msgid "The <guimenu>File</guimenu> Menu"
msgstr "Меню <guimenu>Файл</guimenu>"

#. Tag: menuchoice
#: index.docbook:630
#, no-c-format
msgid ""
"<shortcut> <keycombo>&Ctrl;<keycap>N</keycap></keycombo> </shortcut> "
"<guimenu>File</guimenu> <guimenuitem>New</guimenuitem>"
msgstr ""
"<shortcut> <keycombo>&Ctrl;<keycap>N</keycap></keycombo> </shortcut> "
"<guimenu>Файл</guimenu> <guimenuitem>Создать</guimenuitem>"

#. Tag: para
#: index.docbook:637
#, no-c-format
msgid ""
"<action> Opens an empty toplevel window into which you can load profile "
"data. </action> This action is not really needed, as File/Open will give you "
"a new toplevel window when the current one shows already some data."
msgstr ""

#. Tag: menuchoice
#: index.docbook:645
#, no-c-format
msgid ""
"<shortcut> <keycombo>&Ctrl;<keycap>O</keycap></keycombo> </shortcut> "
"<guimenu>File</guimenu> <guimenuitem>Open</guimenuitem>"
msgstr ""
"<shortcut> <keycombo>&Ctrl;<keycap>O</keycap></keycombo> </shortcut> "
"<guimenu>Файл</guimenu> <guimenuitem>Открыть</guimenuitem>"

#. Tag: para
#: index.docbook:652
#, no-c-format
msgid ""
"<action> Pops up the File Open Dialog to choose a profile data file to be "
"loaded. </action> If there is some data already shown in the current "
"toplevel window, this will open a new window; if you want to open additional "
"profile data in the current window, use File/Add."
msgstr ""

#. Tag: para
#: index.docbook:657
#, no-c-format
msgid ""
"The name of profile data files usually ends in ..-, where and are optional "
"and are used for multiple profile data files belonging to one application "
"run. By loading a file ending only in ., eventually existing data files for "
"this run, but with additional endings, are loaded too."
msgstr ""

#. Tag: para
#: index.docbook:660
#, no-c-format
msgid ""
"Example: If there exist profile data files cachegrind.out.123 and cachegrind."
"out.123.1, by loading the first, the second will be automatically loaded too."
msgstr ""

#. Tag: menuchoice
#: index.docbook:666
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Add</guimenuitem>"
msgstr ""

#. Tag: para
#: index.docbook:670
#, no-c-format
msgid ""
"<action> Adds a profile data file to the current window. </action> Using "
"this, you can force multiple data files to be loaded into the same toplevel "
"window even if they are not from the same run as given by the profile data "
"file naming convention. This can, for example, be used for nearside "
"comparison."
msgstr ""

#. Tag: menuchoice
#: index.docbook:678
#, no-c-format
msgid "<guimenu>File</guimenu> <guimenuitem>Reload</guimenuitem>"
msgstr ""

#. Tag: para
#: index.docbook:682
#, no-c-format
msgid ""
"<action> Reload the profile data. </action> This is most interesting after "
"another profile data file was generated for an already loaded application "
"run."
msgstr ""

#. Tag: menuchoice
#: index.docbook:690
#, no-c-format
msgid ""
"<shortcut> <keycombo>&Ctrl;<keycap>Q</keycap></keycombo> </shortcut> "
"<guimenu>File</guimenu> <guimenuitem>Quit</guimenuitem>"
msgstr ""
"<shortcut> <keycombo>&Ctrl;<keycap>Q</keycap></keycombo> </shortcut> "
"<guimenu>Файл</guimenu> <guimenuitem>Выход</guimenuitem>"

#. Tag: para
#: index.docbook:697
#, no-c-format
msgid "<action>Quits</action> &kappname;"
msgstr "<action>Выйти</action> из &kappname;"

#. Tag: title
#: index.docbook:705
#, no-c-format
msgid "The <guimenu>View</guimenu> Menu"
msgstr ""

#. Tag: menuchoice
#: index.docbook:710
#, no-c-format
msgid "<guimenu>View</guimenu> <guimenuitem>Primary Event Type</guimenuitem>"
msgstr ""

#. Tag: action
#: index.docbook:714 index.docbook:722 index.docbook:730 index.docbook:738
#: index.docbook:746
#, no-c-format
msgid "(To-do)"
msgstr ""

#. Tag: menuchoice
#: index.docbook:718
#, no-c-format
msgid "<guimenu>View</guimenu> <guimenuitem>Secondary Event Type</guimenuitem>"
msgstr ""

#. Tag: menuchoice
#: index.docbook:726
#, no-c-format
msgid "<guimenu>View</guimenu> <guimenuitem>Grouping</guimenuitem>"
msgstr ""

#. Tag: menuchoice
#: index.docbook:734
#, no-c-format
msgid "<guimenu>View</guimenu> <guimenuitem>Layout</guimenuitem>"
msgstr ""

#. Tag: menuchoice
#: index.docbook:742
#, no-c-format
msgid "<guimenu>View</guimenu> <guimenuitem>Split</guimenuitem>"
msgstr ""

#. Tag: title
#: index.docbook:759
#, no-c-format
msgid "Questions and Answers"
msgstr "Вопросы и ответы"

#. Tag: chapter
#: index.docbook:759
#, no-c-format
msgid "&reporting.bugs; &updating.documentation;"
msgstr "&reporting.bugs; &updating.documentation;"

#. Tag: para
#: index.docbook:769
#, no-c-format
msgid "What is &kcachegrind; for? I have no idea."
msgstr ""

#. Tag: para
#: index.docbook:774
#, no-c-format
msgid ""
"&kcachegrind; is a helpful at a later stage in software development, called "
"Profiling. If you don't develop applications, you don't need &kcachegrind;."
msgstr ""
"&kcachegrind; может пригодится на последней стадии разработки программного "
"обеспечения, профилировании. Если вы не занимаетесь разработкой ПО, вам не "
"нужна эта программа."

#. Tag: para
#: index.docbook:784
#, no-c-format
msgid "What is the difference between 'Incl.' and 'Self' ?"
msgstr ""

#. Tag: para
#: index.docbook:789
#, no-c-format
msgid ""
"These are cost attributes for functions regarding some event type. As "
"functions can call each other, it makes sense to distinguish the cost of the "
"function itself ('Self Cost') and the cost including all called functions "
"('Inclusive Cost'). 'Self' is sometimes also referred to as 'Exclusive' "
"costs."
msgstr ""

#. Tag: para
#: index.docbook:791
#, no-c-format
msgid ""
"So, for example, for main(), you will always have a inclusive cost of almost "
"100%, whereas the self cost is negligible when the real work is done in "
"another function."
msgstr ""

#. Tag: para
#: index.docbook:799
#, no-c-format
msgid ""
"The toolbar/menubar of my &kcachegrind; looks so spartanic. Is this normal?"
msgstr ""

#. Tag: para
#: index.docbook:802
#, no-c-format
msgid ""
"Obviously &kcachegrind; is wrongly installed on your system. It is "
"recommended to compile it with the installation prefix to be your system "
"wide &kde; base folder like <command>configure --prefix=/opt/kde3; make "
"install</command>. If you choose another folder like $HOME/kde, you should "
"set the environment variable KDEDIR to this folder before running "
"&kcachegrind;."
msgstr ""

#. Tag: para
#: index.docbook:811
#, no-c-format
msgid ""
"If I double-click on a function down in the Call Graph View, it shows for "
"the function main the same cost as the selected function. Isn't this "
"supposed to be constant 100% ?"
msgstr ""

#. Tag: para
#: index.docbook:816
#, no-c-format
msgid ""
"You have activated a function below main() with cost less than main(). For "
"any function, only that part of the full cost of the function is shown, that "
"is spent while the activated function is running; that is, the cost shown "
"for any function can never be higher than the cost of the activated function."
msgstr ""

#. Tag: title
#: index.docbook:827
#, no-c-format
msgid "Glossary"
msgstr ""

#. Tag: para
#: index.docbook:829
#, no-c-format
msgid "The following is a mixed list of terms."
msgstr ""

#. Tag: para
#: index.docbook:832
#, no-c-format
msgid ""
"Profiling: The process of collecting statistical information about runtime "
"characteristics of program runs."
msgstr ""

#. Tag: para
#: index.docbook:835
#, no-c-format
msgid ""
"Tracing: The process of supervising a program run and storing events "
"happening sorted by a timestap in a output file, the Trace."
msgstr ""

#. Tag: para
#: index.docbook:838
#, no-c-format
msgid ""
"Trace: A sequence of timestamped events that occurred while tracing a "
"program run. Its size is typically linear to the execution time of the "
"program run."
msgstr ""

#. Tag: para
#: index.docbook:841
#, no-c-format
msgid ""
"Profile Data File: A file containing data measured in a profile experiment "
"(or part of) or produced by postprocessing a trace. Its size is typically "
"linear to the code size of the program."
msgstr ""

#. Tag: para
#: index.docbook:844
#, no-c-format
msgid ""
"Profile Data Part (incorrectly used also: Trace Part): Data from a profile "
"data file."
msgstr ""

#. Tag: para
#: index.docbook:847
#, no-c-format
msgid ""
"Profile Experiment: A program run supervised by a profiling tool, producing "
"possibly multiple profile data files from parts and/or threads of the run."
msgstr ""

#. Tag: para
#: index.docbook:850
#, no-c-format
msgid ""
"Profile Project: A configuration for profile experiments used for one "
"program which has to be profiled, perhaps in multiple versions. Comparisons "
"of profile data typically only makes sense between profile data produced in "
"experiments of one profile project."
msgstr ""

#. Tag: para
#: index.docbook:853
#, no-c-format
msgid ""
"Cost Entity: An abstract item related to source code to which event counts "
"can be attributed. Dimensions for cost entities are code location (&eg; "
"source line, function), data location (&eg; accessed data type, data "
"object), execution location (&eg; thread, process), and tuples or triples of "
"the aforementioned positions (&eg; calls, object access from statement, "
"evicted data from cache)."
msgstr ""

#. Tag: para
#: index.docbook:856
#, no-c-format
msgid ""
"Event Type: The kind of event of which costs can be attributed to a cost "
"entity. There exist real event types and inherited event types."
msgstr ""

#. Tag: para
#: index.docbook:859
#, no-c-format
msgid ""
"Real Event Type: A event type that can be measured by a tool. This needs the "
"existence of a sensor for the given event type."
msgstr ""

#. Tag: para
#: index.docbook:862
#, no-c-format
msgid ""
"Inherited Event Type: A virtual event type only visible in the visualization "
"which is defined by a formula to be calculated from real event types."
msgstr ""

#. Tag: para
#: index.docbook:865
#, no-c-format
msgid ""
"Event Costs: Sum of events of some event type occurring while the execution "
"is related to some cost entity. The cost is attributed to the entity."
msgstr ""

#. Tag: title
#: index.docbook:875
#, no-c-format
msgid "Credits and License"
msgstr "Благодарности и лицензия"

#. Tag: para
#: index.docbook:877
#, no-c-format
msgid "&kappname;"
msgstr "&kappname;"

#. Tag: para
#: index.docbook:880
#, no-c-format
msgid ""
"Thanks to Julian Seward for his excellent &valgrind;, and Nicholas "
"Nethercote for the &cachegrind; addition. Without these programs, "
"&kcachegrind; would not exist. Some ideas for this &GUI; were from them, too."
msgstr ""
"Спасибо Юлиану Сьюварду (Julian Seward) за его превосходную &valgrind;, и "
"Николасу Нетеркоту (Nicholas Nethercote) за &cachegrind;. Без них не было бы "
"&kcachegrind;."

#. Tag: para
#: index.docbook:886
#, no-c-format
msgid "And thanks for all the bug reports/suggestions from different users."
msgstr "Спасибо всем за отчёты об ошибках/предложения."

#. Tag: trans_comment
#: index.docbook:891
#, no-c-format
msgid "CREDIT_FOR_TRANSLATORS"
msgstr ""

#. Tag: chapter
#: index.docbook:891
#, no-c-format
msgid "&underFDL;"
msgstr "&underFDL;"

#. Tag: title
#: index.docbook:897
#, no-c-format
msgid "Installation"
msgstr "Установка"

#. Tag: title
#: index.docbook:900
#, no-c-format
msgid "How to obtain &kcachegrind;"
msgstr "Как получить &kcachegrind;"

#. Tag: para
#: index.docbook:902
#, no-c-format
msgid ""
"&kcachegrind; 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 further installation and compile instructions."
msgstr ""

#. Tag: title
#: index.docbook:913
#, no-c-format
msgid "Requirements"
msgstr "Требования"

#. Tag: para
#: index.docbook:915
#, no-c-format
msgid ""
"In order to successfully use &kcachegrind;, you need &kde; 3.x. For "
"generating profile data, &cachegrind; or &calltree;/&callgrind; is recommend."
msgstr ""

#. Tag: title
#: index.docbook:922
#, no-c-format
msgid "Compilation and Installation"
msgstr "Сборка и установка"

#. Tag: sect1
#: index.docbook:922
#, no-c-format
msgid "&install.compile.documentation;"
msgstr "&install.compile.documentation;"

#. Tag: title
#: index.docbook:929
#, no-c-format
msgid "Configuration"
msgstr "Настройка"

#. Tag: para
#: index.docbook:931
#, no-c-format
msgid ""
"All configuration options are either in the configuration dialog or in the "
"context popup menus of the visualizations."
msgstr ""
"Все параметры присутствуют или в окне настроек, или в контекстных меню "
"диаграмм."