python-docs-pl/howto/instrumentation.po at 3.8 · python/python-docs-pl

281 lines (222 loc) · 8.03 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2021, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
# Translators:
# Seweryn Piórkowski <seweryn.piorkowski@gmail.com>, 2020
# Maciej Olko <maciej.olko@gmail.com>, 2020
"Project-Id-Version: Python 3.8\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2021-01-01 16:06+0000\n"
"PO-Revision-Date: 2020-05-30 11:54+0000\n"
"Last-Translator: Maciej Olko <maciej.olko@gmail.com>, 2020\n"
"Language-Team: Polish (https://www.transifex.com/python-doc/teams/5390/pl/)\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Language: pl\n"
"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && "
"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && "
"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n"
msgid "Instrumenting CPython with DTrace and SystemTap"
msgid "author"
msgstr "autor"
msgid "David Malcolm"
msgstr "David Malcolm"
msgid "Łukasz Langa"
msgstr "Łukasz Langa"
"DTrace and SystemTap are monitoring tools, each providing a way to inspect "
"what the processes on a computer system are doing.  They both use domain-"
"specific languages allowing a user to write scripts which:"
msgid "filter which processes are to be observed"
msgid "gather data from the processes of interest"
msgid "generate reports on the data"
"As of Python 3.6, CPython can be built with embedded \"markers\", also known "
"as \"probes\", that can be observed by a DTrace or SystemTap script, making "
"it easier to monitor what the CPython processes on a system are doing."
"DTrace markers are implementation details of the CPython interpreter. No "
"guarantees are made about probe compatibility between versions of CPython. "
"DTrace scripts can stop working or work incorrectly without warning when "
"changing CPython versions."
msgid "Enabling the static markers"
"macOS comes with built-in support for DTrace.  On Linux, in order to build "
"CPython with the embedded markers for SystemTap, the SystemTap development "
"tools must be installed."
msgid "On a Linux machine, this can be done via::"
msgstr "Na Linuksie może to być wykonane przez::"
msgid "or::"
msgstr "lub::"
msgid "CPython must then be configured ``--with-dtrace``:"
"On macOS, you can list available DTrace probes by running a Python process "
"in the background and listing all probes made available by the Python "
"provider::"
"On Linux, you can verify if the SystemTap static markers are present in the "
"built binary by seeing if it contains a \".note.stapsdt\" section."
"If you've built Python as a shared library (with --enable-shared), you need "
"to look instead within the shared library.  For example::"
msgid "Sufficiently modern readelf can print the metadata::"
"The above metadata contains information for SystemTap describing how it can "
"patch strategically-placed machine code instructions to enable the tracing "
"hooks used by a SystemTap script."
msgid "Static DTrace probes"
"The following example DTrace script can be used to show the call/return "
"hierarchy of a Python script, only tracing within the invocation of a "
"function called \"start\". In other words, import-time function invocations "
"are not going to be listed:"
msgid "It can be invoked like this::"
msgid "The output looks like this:"
msgstr "Wynik wygląda tak:"
msgid "Static SystemTap markers"
"The low-level way to use the SystemTap integration is to use the static "
"markers directly.  This requires you to explicitly state the binary file "
"containing them."
"For example, this SystemTap script can be used to show the call/return "
"hierarchy of a Python script:"
msgid "where the columns are:"
msgid "time in microseconds since start of script"
msgid "name of executable"
msgid "PID of process"
"and the remainder indicates the call/return hierarchy as the script executes."
"For a `--enable-shared` build of CPython, the markers are contained within "
"the libpython shared library, and the probe's dotted path needs to reflect "
"this. For example, this line from the above example:"
msgid "should instead read:"
msgid "(assuming a debug build of CPython 3.6)"
msgid "Available static markers"
msgstr "Dostępne znaczniki statyczne"
"This marker indicates that execution of a Python function has begun. It is "
"only triggered for pure-Python (bytecode) functions."
"The filename, function name, and line number are provided back to the "
"tracing script as positional arguments, which must be accessed using "
"``$arg1``, ``$arg2``, ``$arg3``:"
"``$arg1`` : ``(const char *)`` filename, accessible using "
"``user_string($arg1)``"
"``$arg2`` : ``(const char *)`` function name, accessible using "
"``user_string($arg2)``"
msgid "``$arg3`` : ``int`` line number"
"This marker is the converse of :c:func:`function__entry`, and indicates that "
"execution of a Python function has ended (either via ``return``, or via an "
"exception).  It is only triggered for pure-Python (bytecode) functions."
msgid "The arguments are the same as for :c:func:`function__entry`"
"This marker indicates a Python line is about to be executed.  It is the "
"equivalent of line-by-line tracing with a Python profiler.  It is not "
"triggered within C functions."
msgid "The arguments are the same as for :c:func:`function__entry`."
"Fires when the Python interpreter starts a garbage collection cycle. "
"``arg0`` is the generation to scan, like :func:`gc.collect()`."
"Fires when the Python interpreter finishes a garbage collection cycle. "
"``arg0`` is the number of collected objects."
"Fires before :mod:`importlib` attempts to find and load the module. ``arg0`` "
"is the module name."
"Fires after :mod:`importlib`'s find_and_load function is called. ``arg0`` is "
"the module name, ``arg1`` indicates if module was successfully loaded."
"Fires when :func:`sys.audit` or :c:func:`PySys_Audit` is called. ``arg0`` is "
"the event name as C string, ``arg1`` is a :c:type:`PyObject` pointer to a "
"tuple object."
msgid "SystemTap Tapsets"
"The higher-level way to use the SystemTap integration is to use a "
"\"tapset\": SystemTap's equivalent of a library, which hides some of the "
"lower-level details of the static markers."
msgid "Here is a tapset file, based on a non-shared build of CPython:"
"If this file is installed in SystemTap's tapset directory (e.g. ``/usr/share/"
"systemtap/tapset``), then these additional probepoints become available:"
"This probe point indicates that execution of a Python function has begun. It "
"is only triggered for pure-Python (bytecode) functions."
"This probe point is the converse of ``python.function.return``, and "
"indicates that execution of a Python function has ended (either via "
"``return``, or via an exception).  It is only triggered for pure-Python "
"(bytecode) functions."
msgid "Examples"
msgstr "Przykłady"
"This SystemTap script uses the tapset above to more cleanly implement the "
"example given above of tracing the Python function-call hierarchy, without "
"needing to directly name the static markers:"
"The following script uses the tapset above to provide a top-like view of all "
"running CPython code, showing the top 20 most frequently-entered bytecode "
"frames, each second, across the whole system:"
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

FilesExpand file tree

instrumentation.po

Latest commit

History

instrumentation.po

File metadata and controls
