Skip to content

Traducido archivo c-api/perfmaps #3363

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 31, 2025
Merged

Traducido archivo c-api/perfmaps #3363

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
68116c7
Traducido archivo c-api/perfmaps
srmorita Jan 28, 2025
ae4a6ac
Observations Fixed and complete translation
srmorita Jan 29, 2025
2289c47
Observations fixed
srmorita Jan 31, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Next Next commit
Traducido archivo c-api/perfmaps
  • Loading branch information
@srmorita
srmorita committed Jan 28, 2025
commit 68116c7b7e128415c233cb71b5b228c9a7ad8caf
41 changes: 30 additions & 11 deletions c-api/perfmaps.po
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,15 +10,16 @@ msgstr ""
"Project-Id-Version: Python en Español 3.12\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-21 16:38-0300\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language: es\n"
"PO-Revision-Date: 2025-01-28 17:53-0300\n"
"Last-Translator: srmorita <fr.morac@duocuc.cl>\n"
"Language-Team: es <LL@li.org>\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"Language: es\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=utf-8\n"
"Content-Transfer-Encoding: 8bit\n"
"Plural-Forms: nplurals=2; plural=(n != 1);\n"
"Generated-By: Babel 2.16.0\n"
"X-Generator: Poedit 3.5\n"

#: ../Doc/c-api/perfmaps.rst:6
msgid "Support for Perf Maps"
Expand All @@ -28,12 +29,12 @@ msgstr ""
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`` "
"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>`_."
"Perf tool <https://git.kernel.org/pub/scm/linux/ kernel/git/torvalds/"
"linux.git/tree/tools/perf/Documentation/jit-interface.txt>`_."
msgstr ""

#: ../Doc/c-api/perfmaps.rst:16
Expand All @@ -53,9 +54,9 @@ 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."
"need to call this explicitly; just "
"use :c:func:`PyUnstable_WritePerfMapEntry` and it will initialize the state "
"on first call."
msgstr ""

#: ../Doc/c-api/perfmaps.rst:29
Expand All @@ -64,25 +65,38 @@ msgid ""
"file, or ``-2`` on failure to create a lock. Check ``errno`` for more "
"information about the cause of a failure."
msgstr ""
"Retorna ``0`` en caso de éxito, ``-1`` en caso de fallo al crear/abrir el "
"fichero perf map, o ``-2`` en caso de fallo al crear un bloqueo. Comprueba "
"``errno`` para más información sobre la causa de un fallo."

#: ../Doc/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 ""
"Escribe una única entrada en el fichero ``/tmp/perf-$pid.map``. Esta función "
"es de hilo seguro. Aquí hay un ejemplo de entrada::"

# creo que esto debe quedar igual. Es solo código fuente.
#: ../Doc/c-api/perfmaps.rst:38
#, fuzzy
msgid ""
"# address size name\n"
"7f3529fcf759 b py::bar:/run/t.py"
msgstr ""
"# address size name\n"
"7f3529fcf759 b py::bar:/run/t.py"

#: ../Doc/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 ""
"Llamará a :c:func:`PyUnstable_PerfMapState_Init` antes de escribir la "
"entrada, si el fichero perf map no está ya abierto. Retorna ``0`` en caso de "
"éxito, o los mismos códigos de error "
"que :c:func:`PyUnstable_PerfMapState_Init` en caso de fallo."

#: ../Doc/c-api/perfmaps.rst:47
msgid ""
Expand All @@ -91,3 +105,8 @@ msgid ""
"general, there shouldn't be a reason to explicitly call this, except to "
"handle specific scenarios such as forking."
msgstr ""
"Cierra el fichero perf map abierto "
"por :c:func:`PyUnstable_PerfMapState_Init`. Esto es llamado por el propio "
"tiempo de ejecución durante el cierre del intérprete. En general, no debería "
"haber una razón para llamar explícitamente a esto, excepto para manejar "
"escenarios específicos como la bifurcación."