python-docs-fr/howto/gdb_helpers.po at 3.13 · python/python-docs-fr

396 lines (330 loc) · 11.5 KB
# SOME DESCRIPTIVE TITLE.
# Copyright (C) 2001-2024, Python Software Foundation
# This file is distributed under the same license as the Python package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
"Project-Id-Version: Python 3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-11-01 00:16+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
"Language: fr\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: howto/gdb_helpers.rst:5
msgid "Debugging C API extensions and CPython Internals with GDB"
#: howto/gdb_helpers.rst:9
"This document explains how the Python GDB extension, ``python-gdb.py``, can "
"be used with the GDB debugger to debug CPython extensions and the CPython "
"interpreter itself."
#: howto/gdb_helpers.rst:13
"When debugging low-level problems such as crashes or deadlocks, a low-level "
"debugger, such as GDB, is useful to diagnose and correct the issue. By "
"default, GDB (or any of its front-ends) doesn't support high-level "
"information specific to the CPython interpreter."
#: howto/gdb_helpers.rst:18
"The ``python-gdb.py`` extension adds CPython interpreter information to GDB. "
"The extension helps introspect the stack of currently executing Python "
"functions. Given a Python object represented by a :c:expr:`PyObject *` "
"pointer, the extension surfaces the type and value of the object."
#: howto/gdb_helpers.rst:23
"Developers who are working on CPython extensions or tinkering with parts of "
"CPython that are written in C can use this document to learn how to use the "
"``python-gdb.py`` extension with GDB."
#: howto/gdb_helpers.rst:29
"This document assumes that you are familiar with the basics of GDB and the "
"CPython C API. It consolidates guidance from the `devguide <https://devguide."
"python.org>`_  and the `Python wiki <https://wiki.python.org/moin/"
"DebuggingWithGdb>`_."
#: howto/gdb_helpers.rst:36
msgid "Prerequisites"
#: howto/gdb_helpers.rst:38
msgid "You need to have:"
#: howto/gdb_helpers.rst:40
"GDB 7 or later. (For earlier versions of GDB, see ``Misc/gdbinit`` in the "
"sources of Python 3.11 or earlier.)"
#: howto/gdb_helpers.rst:42
"GDB-compatible debugging information for Python and any extension you are "
"debugging."
#: howto/gdb_helpers.rst:44
msgid "The ``python-gdb.py`` extension."
#: howto/gdb_helpers.rst:46
"The extension is built with Python, but might be distributed separately or "
"not at all. Below, we include tips for a few common systems as examples. "
"Note that even if the instructions match your system, they might be outdated."
#: howto/gdb_helpers.rst:52
msgid "Setup with Python built from source"
#: howto/gdb_helpers.rst:54
"When you build CPython from source, debugging information should be "
"available, and the build should add a ``python-gdb.py`` file to the root "
"directory of your repository."
#: howto/gdb_helpers.rst:58
"To activate support, you must add the directory containing ``python-gdb.py`` "
"to GDB's \"auto-load-safe-path\". If you haven't done this, recent versions "
"of GDB will print out a warning with instructions on how to do this."
#: howto/gdb_helpers.rst:65
"If you do not see instructions for your version of GDB, put this in your "
"configuration file (``~/.gdbinit`` or ``~/.config/gdb/gdbinit``)::"
#: howto/gdb_helpers.rst:70
msgid "You can also add multiple paths, separated by ``:``."
#: howto/gdb_helpers.rst:74
msgid "Setup for Python from a Linux distro"
#: howto/gdb_helpers.rst:76
"Most Linux systems provide debug information for the system Python in a "
"package called ``python-debuginfo``, ``python-dbg`` or similar. For example:"
#: howto/gdb_helpers.rst:80
msgid "Fedora:"
#: howto/gdb_helpers.rst:87
msgid "Ubuntu:"
#: howto/gdb_helpers.rst:93
"On several recent Linux systems, GDB can download debugging symbols "
"automatically using *debuginfod*. However, this will not install the "
"``python-gdb.py`` extension; you generally do need to install the debug info "
"package separately."
#: howto/gdb_helpers.rst:100
msgid "Using the Debug build and Development mode"
#: howto/gdb_helpers.rst:102
msgid "For easier debugging, you might want to:"
#: howto/gdb_helpers.rst:104
"Use a :ref:`debug build <debug-build>` of Python. (When building from "
"source, use ``configure --with-pydebug``. On Linux distros, install and run "
"a package like ``python-debug`` or ``python-dbg``, if available.)"
#: howto/gdb_helpers.rst:107
msgid "Use the runtime :ref:`development mode <devmode>` (``-X dev``)."
#: howto/gdb_helpers.rst:109
"Both enable extra assertions and disable some optimizations. Sometimes this "
"hides the bug you are trying to find, but in most cases they make the "
"process easier."
#: howto/gdb_helpers.rst:115
msgid "Using the ``python-gdb`` extension"
#: howto/gdb_helpers.rst:117
"When the extension is loaded, it provides two main features: pretty printers "
"for Python values, and additional commands."
#: howto/gdb_helpers.rst:121
msgid "Pretty-printers"
#: howto/gdb_helpers.rst:123
"This is what a GDB backtrace looks like (truncated) when this extension is "
"enabled::"
#: howto/gdb_helpers.rst:142
"Notice how the dictionary argument to ``PyDict_GetItemString`` is displayed "
"as its ``repr()``, rather than an opaque ``PyObject *`` pointer."
#: howto/gdb_helpers.rst:145
"The extension works by supplying a custom printing routine for values of "
"type ``PyObject *``.  If you need to access lower-level details of an "
"object, then cast the value to a pointer of the appropriate type.  For "
"example::"
#: howto/gdb_helpers.rst:168
"Note that the pretty-printers do not actually call ``repr()``. For basic "
"types, they try to match its result closely."
#: howto/gdb_helpers.rst:171
"An area that can be confusing is that the custom printer for some types look "
"a lot like GDB's built-in printer for standard types.  For example, the "
"pretty-printer for a Python ``int`` (:c:expr:`PyLongObject *`) gives a "
"representation that is not distinguishable from one of a regular machine-"
"level integer::"
#: howto/gdb_helpers.rst:183
"The internal structure can be revealed with a cast to :c:expr:`PyLongObject "
#: howto/gdb_helpers.rst:185
"(gdb) p *(PyLongObject*)some_python_integer $5 = {ob_base = {ob_base = "
"{ob_refcnt = 8, ob_type = 0x3dad39f5e0}, ob_size = 1}, ob_digit = {42}}"
#: howto/gdb_helpers.rst:189
"A similar confusion can arise with the ``str`` type, where the output looks "
"a lot like gdb's built-in printer for ``char *``::"
#: howto/gdb_helpers.rst:195
"The pretty-printer for ``str`` instances defaults to using single-quotes (as "
"does Python's ``repr`` for strings) whereas the standard printer for ``char "
"*`` values uses double-quotes and contains a hexadecimal address::"
#: howto/gdb_helpers.rst:202
"Again, the implementation details can be revealed with a cast to :c:expr:"
"`PyUnicodeObject *`::"
#: howto/gdb_helpers.rst:210
msgid "``py-list``"
#: howto/gdb_helpers.rst:212
"The extension adds a ``py-list`` command, which lists the Python source code "
"(if any) for the current frame in the selected thread.  The current line is "
"marked with a \">\"::"
#: howto/gdb_helpers.rst:229
"Use ``py-list START`` to list at a different line number within the Python "
"source, and ``py-list START,END`` to list a specific range of lines within "
"the Python source."
#: howto/gdb_helpers.rst:234
msgid "``py-up`` and ``py-down``"
#: howto/gdb_helpers.rst:236
"The ``py-up`` and ``py-down`` commands are analogous to GDB's regular ``up`` "
"and ``down`` commands, but try to move at the level of CPython frames, "
"rather than C frames."
#: howto/gdb_helpers.rst:240
"GDB is not always able to read the relevant frame information, depending on "
"the optimization level with which CPython was compiled. Internally, the "
"commands look for C frames that are executing the default frame evaluation "
"function (that is, the core bytecode interpreter loop within CPython) and "
"look up the value of the related ``PyFrameObject *``."
#: howto/gdb_helpers.rst:246
msgid "They emit the frame number (at the C level) within the thread."
#: howto/gdb_helpers.rst:320
msgid "For example::"
msgstr "Par exemple ::"
#: howto/gdb_helpers.rst:261
msgid "so we're at the top of the Python stack."
#: howto/gdb_helpers.rst:263
"The frame numbers correspond to those displayed by GDB's standard "
"``backtrace`` command. The command skips C frames which are not executing "
"Python code."
#: howto/gdb_helpers.rst:267
msgid "Going back down::"
#: howto/gdb_helpers.rst:289
msgid "and we're at the bottom of the Python stack."
#: howto/gdb_helpers.rst:291
"Note that in Python 3.12 and newer, the same C stack frame can be used for "
"multiple Python stack frames. This means that ``py-up`` and ``py-down`` may "
"move multiple Python frames at once. For example::"
#: howto/gdb_helpers.rst:315
msgid "``py-bt``"
#: howto/gdb_helpers.rst:317
"The ``py-bt`` command attempts to display a Python-level backtrace of the "
"current thread."
#: howto/gdb_helpers.rst:336
"The frame numbers correspond to those displayed by GDB's standard "
"``backtrace`` command."
#: howto/gdb_helpers.rst:340
msgid "``py-print``"
#: howto/gdb_helpers.rst:342
"The ``py-print`` command looks up a Python name and tries to print it. It "
"looks in locals within the current thread, then globals, then finally "
"builtins::"
#: howto/gdb_helpers.rst:356
"If the current C frame corresponds to multiple Python frames, ``py-print`` "
"only considers the first one."
#: howto/gdb_helpers.rst:360
msgid "``py-locals``"
#: howto/gdb_helpers.rst:362
"The ``py-locals`` command looks up all Python locals within the current "
"Python frame in the selected thread, and prints their representations::"
#: howto/gdb_helpers.rst:370
"If the current C frame corresponds to multiple Python frames, locals from "
"all of them will be shown::"
#: howto/gdb_helpers.rst:390
msgid "Use with GDB commands"
#: howto/gdb_helpers.rst:392
"The extension commands complement GDB's built-in commands. For example, you "
"can use a frame numbers shown by ``py-bt`` with the ``frame`` command to go "
"a specific frame within the selected thread, like this::"
#: howto/gdb_helpers.rst:411
"The ``info threads`` command will give you a list of the threads within the "
"process, and you can use the ``thread`` command to select a different one::"
#: howto/gdb_helpers.rst:419
"You can use ``thread apply all COMMAND`` or (``t a a COMMAND`` for short) to "
"run a command on all threads.  With ``py-bt``, this lets you see what every "
"thread is doing at the Python level::"
Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

FilesExpand file tree

gdb_helpers.po

Latest commit

History

gdb_helpers.po

File metadata and controls
