-
Notifications
You must be signed in to change notification settings - Fork 10
Expand file tree
/
Copy pathperfmaps.po
More file actions
58 lines (48 loc) · 2.94 KB
/
Copy pathperfmaps.po
File metadata and controls
58 lines (48 loc) · 2.94 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2025, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.13\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-10 02:51+0330\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: c-api/perfmaps.rst:6
msgid "Support for Perf Maps"
msgstr ""
#: c-api/perfmaps.rst:8
msgid "On supported platforms (as of this writing, only Linux), the runtime can take advantage of *perf map files* to make Python functions visible to an external profiling tool (such as `perf <https://perf.wiki.kernel.org/index.php/Main_Page>`_). A running process may create a file in the ``/tmp`` directory, which contains entries that can map a section of executable code to a name. This interface is described in the `documentation of the Linux Perf tool <https://git.kernel.org/pub/scm/linux/ kernel/git/torvalds/linux.git/tree/tools/perf/Documentation/jit-interface.txt>`_."
msgstr ""
#: c-api/perfmaps.rst:16
msgid "In Python, these helper APIs can be used by libraries and features that rely on generating machine code on the fly."
msgstr ""
#: c-api/perfmaps.rst:19
msgid "Note that holding the Global Interpreter Lock (GIL) is not required for these APIs."
msgstr ""
#: c-api/perfmaps.rst:23
msgid "Open the ``/tmp/perf-$pid.map`` file, unless it's already opened, and create a lock to ensure thread-safe writes to the file (provided the writes are done through :c:func:`PyUnstable_WritePerfMapEntry`). Normally, there's no need to call this explicitly; just use :c:func:`PyUnstable_WritePerfMapEntry` and it will initialize the state on first call."
msgstr ""
#: c-api/perfmaps.rst:29
msgid "Returns ``0`` on success, ``-1`` on failure to create/open the perf map file, or ``-2`` on failure to create a lock. Check ``errno`` for more information about the cause of a failure."
msgstr ""
#: c-api/perfmaps.rst:35
msgid "Write one single entry to the ``/tmp/perf-$pid.map`` file. This function is thread safe. Here is what an example entry looks like::"
msgstr ""
#: c-api/perfmaps.rst:38
msgid "# address size name\n"
"7f3529fcf759 b py::bar:/run/t.py"
msgstr ""
#: c-api/perfmaps.rst:41
msgid "Will call :c:func:`PyUnstable_PerfMapState_Init` before writing the entry, if the perf map file is not already opened. Returns ``0`` on success, or the same error codes as :c:func:`PyUnstable_PerfMapState_Init` on failure."
msgstr ""
#: c-api/perfmaps.rst:47
msgid "Close the perf map file opened by :c:func:`PyUnstable_PerfMapState_Init`. This is called by the runtime itself during interpreter shut-down. In general, there shouldn't be a reason to explicitly call this, except to handle specific scenarios such as forking."
msgstr ""