|
| 1 | +# SOME DESCRIPTIVE TITLE. |
| 2 | +# Copyright (C) 2001-2024, Python Software Foundation |
| 3 | +# This file is distributed under the same license as the Python package. |
| 4 | +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. |
| 5 | +# |
| 6 | +# Translators: |
| 7 | +# Stefan Ocetkiewicz <stefan.ocetkiewicz@gmail.com>, 2024 |
| 8 | +# |
| 9 | +#, fuzzy |
| 10 | +msgid "" |
| 11 | +msgstr "" |
| 12 | +"Project-Id-Version: Python 3.12\n" |
| 13 | +"Report-Msgid-Bugs-To: \n" |
| 14 | +"POT-Creation-Date: 2024-02-25 01:09+0000\n" |
| 15 | +"PO-Revision-Date: 2024-02-25 01:11+0000\n" |
| 16 | +"Last-Translator: Stefan Ocetkiewicz <stefan.ocetkiewicz@gmail.com>, 2024\n" |
| 17 | +"Language-Team: Polish (https://app.transifex.com/python-doc/teams/5390/pl/)\n" |
| 18 | +"MIME-Version: 1.0\n" |
| 19 | +"Content-Type: text/plain; charset=UTF-8\n" |
| 20 | +"Content-Transfer-Encoding: 8bit\n" |
| 21 | +"Language: pl\n" |
| 22 | +"Plural-Forms: nplurals=4; plural=(n==1 ? 0 : (n%10>=2 && n%10<=4) && " |
| 23 | +"(n%100<12 || n%100>14) ? 1 : n!=1 && (n%10>=0 && n%10<=1) || (n%10>=5 && " |
| 24 | +"n%10<=9) || (n%100>=12 && n%100<=14) ? 2 : 3);\n" |
| 25 | + |
| 26 | +msgid "Debugging C API extensions and CPython Internals with GDB" |
| 27 | +msgstr "" |
| 28 | + |
| 29 | +msgid "" |
| 30 | +"This document explains how the Python GDB extension, ``python-gdb.py``, can " |
| 31 | +"be used with the GDB debugger to debug CPython extensions and the CPython " |
| 32 | +"interpreter itself." |
| 33 | +msgstr "" |
| 34 | + |
| 35 | +msgid "" |
| 36 | +"When debugging low-level problems such as crashes or deadlocks, a low-level " |
| 37 | +"debugger, such as GDB, is useful to diagnose and correct the issue. By " |
| 38 | +"default, GDB (or any of its front-ends) doesn't support high-level " |
| 39 | +"information specific to the CPython interpreter." |
| 40 | +msgstr "" |
| 41 | + |
| 42 | +msgid "" |
| 43 | +"The ``python-gdb.py`` extension adds CPython interpreter information to GDB. " |
| 44 | +"The extension helps introspect the stack of currently executing Python " |
| 45 | +"functions. Given a Python object represented by a :c:expr:`PyObject *` " |
| 46 | +"pointer, the extension surfaces the type and value of the object." |
| 47 | +msgstr "" |
| 48 | + |
| 49 | +msgid "" |
| 50 | +"Developers who are working on CPython extensions or tinkering with parts of " |
| 51 | +"CPython that are written in C can use this document to learn how to use the " |
| 52 | +"``python-gdb.py`` extension with GDB." |
| 53 | +msgstr "" |
| 54 | + |
| 55 | +msgid "" |
| 56 | +"This document assumes that you are familiar with the basics of GDB and the " |
| 57 | +"CPython C API. It consolidates guidance from the `devguide <https://devguide." |
| 58 | +"python.org>`_ and the `Python wiki <https://wiki.python.org/moin/" |
| 59 | +"DebuggingWithGdb>`_." |
| 60 | +msgstr "" |
| 61 | + |
| 62 | +msgid "Prerequisites" |
| 63 | +msgstr "" |
| 64 | + |
| 65 | +msgid "You need to have:" |
| 66 | +msgstr "" |
| 67 | + |
| 68 | +msgid "" |
| 69 | +"GDB 7 or later. (For earlier versions of GDB, see ``Misc/gdbinit`` in the " |
| 70 | +"sources of Python 3.11 or earlier.)" |
| 71 | +msgstr "" |
| 72 | + |
| 73 | +msgid "" |
| 74 | +"GDB-compatible debugging information for Python and any extension you are " |
| 75 | +"debugging." |
| 76 | +msgstr "" |
| 77 | + |
| 78 | +msgid "The ``python-gdb.py`` extension." |
| 79 | +msgstr "" |
| 80 | + |
| 81 | +msgid "" |
| 82 | +"The extension is built with Python, but might be distributed separately or " |
| 83 | +"not at all. Below, we include tips for a few common systems as examples. " |
| 84 | +"Note that even if the instructions match your system, they might be outdated." |
| 85 | +msgstr "" |
| 86 | + |
| 87 | +msgid "Setup with Python built from source" |
| 88 | +msgstr "" |
| 89 | + |
| 90 | +msgid "" |
| 91 | +"When you build CPython from source, debugging information should be " |
| 92 | +"available, and the build should add a ``python-gdb.py`` file to the root " |
| 93 | +"directory of your repository." |
| 94 | +msgstr "" |
| 95 | + |
| 96 | +msgid "" |
| 97 | +"To activate support, you must add the directory containing ``python-gdb.py`` " |
| 98 | +"to GDB's \"auto-load-safe-path\". If you haven't done this, recent versions " |
| 99 | +"of GDB will print out a warning with instructions on how to do this." |
| 100 | +msgstr "" |
| 101 | + |
| 102 | +msgid "" |
| 103 | +"If you do not see instructions for your version of GDB, put this in your " |
| 104 | +"configuration file (``~/.gdbinit`` or ``~/.config/gdb/gdbinit``)::" |
| 105 | +msgstr "" |
| 106 | + |
| 107 | +msgid "You can also add multiple paths, separated by ``:``." |
| 108 | +msgstr "" |
| 109 | + |
| 110 | +msgid "Setup for Python from a Linux distro" |
| 111 | +msgstr "" |
| 112 | + |
| 113 | +msgid "" |
| 114 | +"Most Linux systems provide debug information for the system Python in a " |
| 115 | +"package called ``python-debuginfo``, ``python-dbg`` or similar. For example:" |
| 116 | +msgstr "" |
| 117 | + |
| 118 | +msgid "Fedora:" |
| 119 | +msgstr "" |
| 120 | + |
| 121 | +msgid "Ubuntu:" |
| 122 | +msgstr "" |
| 123 | + |
| 124 | +msgid "" |
| 125 | +"On several recent Linux systems, GDB can download debugging symbols " |
| 126 | +"automatically using *debuginfod*. However, this will not install the " |
| 127 | +"``python-gdb.py`` extension; you generally do need to install the debug info " |
| 128 | +"package separately." |
| 129 | +msgstr "" |
| 130 | + |
| 131 | +msgid "Using the Debug build and Development mode" |
| 132 | +msgstr "" |
| 133 | + |
| 134 | +msgid "For easier debugging, you might want to:" |
| 135 | +msgstr "" |
| 136 | + |
| 137 | +msgid "" |
| 138 | +"Use a :ref:`debug build <debug-build>` of Python. (When building from " |
| 139 | +"source, use ``configure --with-pydebug``. On Linux distros, install and run " |
| 140 | +"a package like ``python-debug`` or ``python-dbg``, if available.)" |
| 141 | +msgstr "" |
| 142 | + |
| 143 | +msgid "Use the runtime :ref:`development mode <devmode>` (``-X dev``)." |
| 144 | +msgstr "" |
| 145 | + |
| 146 | +msgid "" |
| 147 | +"Both enable extra assertions and disable some optimizations. Sometimes this " |
| 148 | +"hides the bug you are trying to find, but in most cases they make the " |
| 149 | +"process easier." |
| 150 | +msgstr "" |
| 151 | + |
| 152 | +msgid "Using the ``python-gdb`` extension" |
| 153 | +msgstr "" |
| 154 | + |
| 155 | +msgid "" |
| 156 | +"When the extension is loaded, it provides two main features: pretty printers " |
| 157 | +"for Python values, and additional commands." |
| 158 | +msgstr "" |
| 159 | + |
| 160 | +msgid "Pretty-printers" |
| 161 | +msgstr "" |
| 162 | + |
| 163 | +msgid "" |
| 164 | +"This is what a GDB backtrace looks like (truncated) when this extension is " |
| 165 | +"enabled::" |
| 166 | +msgstr "" |
| 167 | + |
| 168 | +msgid "" |
| 169 | +"Notice how the dictionary argument to ``PyDict_GetItemString`` is displayed " |
| 170 | +"as its ``repr()``, rather than an opaque ``PyObject *`` pointer." |
| 171 | +msgstr "" |
| 172 | + |
| 173 | +msgid "" |
| 174 | +"The extension works by supplying a custom printing routine for values of " |
| 175 | +"type ``PyObject *``. If you need to access lower-level details of an " |
| 176 | +"object, then cast the value to a pointer of the appropriate type. For " |
| 177 | +"example::" |
| 178 | +msgstr "" |
| 179 | + |
| 180 | +msgid "" |
| 181 | +"Note that the pretty-printers do not actually call ``repr()``. For basic " |
| 182 | +"types, they try to match its result closely." |
| 183 | +msgstr "" |
| 184 | + |
| 185 | +msgid "" |
| 186 | +"An area that can be confusing is that the custom printer for some types look " |
| 187 | +"a lot like GDB's built-in printer for standard types. For example, the " |
| 188 | +"pretty-printer for a Python ``int`` (:c:expr:`PyLongObject *`) gives a " |
| 189 | +"representation that is not distinguishable from one of a regular machine-" |
| 190 | +"level integer::" |
| 191 | +msgstr "" |
| 192 | + |
| 193 | +msgid "" |
| 194 | +"The internal structure can be revealed with a cast to :c:expr:`PyLongObject " |
| 195 | +"*`:" |
| 196 | +msgstr "" |
| 197 | + |
| 198 | +msgid "" |
| 199 | +"(gdb) p *(PyLongObject*)some_python_integer $5 = {ob_base = {ob_base = " |
| 200 | +"{ob_refcnt = 8, ob_type = 0x3dad39f5e0}, ob_size = 1}, ob_digit = {42}}" |
| 201 | +msgstr "" |
| 202 | + |
| 203 | +msgid "" |
| 204 | +"A similar confusion can arise with the ``str`` type, where the output looks " |
| 205 | +"a lot like gdb's built-in printer for ``char *``::" |
| 206 | +msgstr "" |
| 207 | + |
| 208 | +msgid "" |
| 209 | +"The pretty-printer for ``str`` instances defaults to using single-quotes (as " |
| 210 | +"does Python's ``repr`` for strings) whereas the standard printer for ``char " |
| 211 | +"*`` values uses double-quotes and contains a hexadecimal address::" |
| 212 | +msgstr "" |
| 213 | + |
| 214 | +msgid "" |
| 215 | +"Again, the implementation details can be revealed with a cast to :c:expr:" |
| 216 | +"`PyUnicodeObject *`::" |
| 217 | +msgstr "" |
| 218 | + |
| 219 | +msgid "``py-list``" |
| 220 | +msgstr "" |
| 221 | + |
| 222 | +msgid "" |
| 223 | +"The extension adds a ``py-list`` command, which lists the Python source code " |
| 224 | +"(if any) for the current frame in the selected thread. The current line is " |
| 225 | +"marked with a \">\"::" |
| 226 | +msgstr "" |
| 227 | + |
| 228 | +msgid "" |
| 229 | +"Use ``py-list START`` to list at a different line number within the Python " |
| 230 | +"source, and ``py-list START,END`` to list a specific range of lines within " |
| 231 | +"the Python source." |
| 232 | +msgstr "" |
| 233 | + |
| 234 | +msgid "``py-up`` and ``py-down``" |
| 235 | +msgstr "" |
| 236 | + |
| 237 | +msgid "" |
| 238 | +"The ``py-up`` and ``py-down`` commands are analogous to GDB's regular ``up`` " |
| 239 | +"and ``down`` commands, but try to move at the level of CPython frames, " |
| 240 | +"rather than C frames." |
| 241 | +msgstr "" |
| 242 | + |
| 243 | +msgid "" |
| 244 | +"GDB is not always able to read the relevant frame information, depending on " |
| 245 | +"the optimization level with which CPython was compiled. Internally, the " |
| 246 | +"commands look for C frames that are executing the default frame evaluation " |
| 247 | +"function (that is, the core bytecode interpreter loop within CPython) and " |
| 248 | +"look up the value of the related ``PyFrameObject *``." |
| 249 | +msgstr "" |
| 250 | + |
| 251 | +msgid "They emit the frame number (at the C level) within the thread." |
| 252 | +msgstr "" |
| 253 | + |
| 254 | +msgid "For example::" |
| 255 | +msgstr "Na przykład::" |
| 256 | + |
| 257 | +msgid "so we're at the top of the Python stack." |
| 258 | +msgstr "" |
| 259 | + |
| 260 | +msgid "" |
| 261 | +"The frame numbers correspond to those displayed by GDB's standard " |
| 262 | +"``backtrace`` command. The command skips C frames which are not executing " |
| 263 | +"Python code." |
| 264 | +msgstr "" |
| 265 | + |
| 266 | +msgid "Going back down::" |
| 267 | +msgstr "" |
| 268 | + |
| 269 | +msgid "and we're at the bottom of the Python stack." |
| 270 | +msgstr "" |
| 271 | + |
| 272 | +msgid "" |
| 273 | +"Note that in Python 3.12 and newer, the same C stack frame can be used for " |
| 274 | +"multiple Python stack frames. This means that ``py-up`` and ``py-down`` may " |
| 275 | +"move multiple Python frames at once. For example::" |
| 276 | +msgstr "" |
| 277 | + |
| 278 | +msgid "``py-bt``" |
| 279 | +msgstr "" |
| 280 | + |
| 281 | +msgid "" |
| 282 | +"The ``py-bt`` command attempts to display a Python-level backtrace of the " |
| 283 | +"current thread." |
| 284 | +msgstr "" |
| 285 | + |
| 286 | +msgid "" |
| 287 | +"The frame numbers correspond to those displayed by GDB's standard " |
| 288 | +"``backtrace`` command." |
| 289 | +msgstr "" |
| 290 | + |
| 291 | +msgid "``py-print``" |
| 292 | +msgstr "" |
| 293 | + |
| 294 | +msgid "" |
| 295 | +"The ``py-print`` command looks up a Python name and tries to print it. It " |
| 296 | +"looks in locals within the current thread, then globals, then finally " |
| 297 | +"builtins::" |
| 298 | +msgstr "" |
| 299 | + |
| 300 | +msgid "" |
| 301 | +"If the current C frame corresponds to multiple Python frames, ``py-print`` " |
| 302 | +"only considers the first one." |
| 303 | +msgstr "" |
| 304 | + |
| 305 | +msgid "``py-locals``" |
| 306 | +msgstr "" |
| 307 | + |
| 308 | +msgid "" |
| 309 | +"The ``py-locals`` command looks up all Python locals within the current " |
| 310 | +"Python frame in the selected thread, and prints their representations::" |
| 311 | +msgstr "" |
| 312 | + |
| 313 | +msgid "" |
| 314 | +"If the current C frame corresponds to multiple Python frames, locals from " |
| 315 | +"all of them will be shown::" |
| 316 | +msgstr "" |
| 317 | + |
| 318 | +msgid "Use with GDB commands" |
| 319 | +msgstr "" |
| 320 | + |
| 321 | +msgid "" |
| 322 | +"The extension commands complement GDB's built-in commands. For example, you " |
| 323 | +"can use a frame numbers shown by ``py-bt`` with the ``frame`` command to go " |
| 324 | +"a specific frame within the selected thread, like this::" |
| 325 | +msgstr "" |
| 326 | + |
| 327 | +msgid "" |
| 328 | +"The ``info threads`` command will give you a list of the threads within the " |
| 329 | +"process, and you can use the ``thread`` command to select a different one::" |
| 330 | +msgstr "" |
| 331 | + |
| 332 | +msgid "" |
| 333 | +"You can use ``thread apply all COMMAND`` or (``t a a COMMAND`` for short) to " |
| 334 | +"run a command on all threads. With ``py-bt``, this lets you see what every " |
| 335 | +"thread is doing at the Python level::" |
| 336 | +msgstr "" |
0 commit comments