# SOME DESCRIPTIVE TITLE. # Copyright (C) 2001-2022, Python Software Foundation # This file is distributed under the same license as the Python package. # # Translators: # Ching-Lung Chuang, 2015 msgid "" msgstr "" "Project-Id-Version: Python 3.12\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-08-01 00:03+0000\n" "PO-Revision-Date: 2018-05-23 14:06+0000\n" "Last-Translator: Adrian Liaw \n" "Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-" "tw)\n" "Language: zh_TW\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" #: ../../c-api/memory.rst:8 msgid "Memory Management" msgstr "記憶體管理" #: ../../c-api/memory.rst:17 msgid "Overview" msgstr "總覽" #: ../../c-api/memory.rst:19 msgid "" "Memory management in Python involves a private heap containing all Python " "objects and data structures. The management of this private heap is ensured " "internally by the *Python memory manager*. The Python memory manager has " "different components which deal with various dynamic storage management " "aspects, like sharing, segmentation, preallocation or caching." msgstr "" #: ../../c-api/memory.rst:25 msgid "" "At the lowest level, a raw memory allocator ensures that there is enough " "room in the private heap for storing all Python-related data by interacting " "with the memory manager of the operating system. On top of the raw memory " "allocator, several object-specific allocators operate on the same heap and " "implement distinct memory management policies adapted to the peculiarities " "of every object type. For example, integer objects are managed differently " "within the heap than strings, tuples or dictionaries because integers imply " "different storage requirements and speed/space tradeoffs. The Python memory " "manager thus delegates some of the work to the object-specific allocators, " "but ensures that the latter operate within the bounds of the private heap." msgstr "" #: ../../c-api/memory.rst:36 msgid "" "It is important to understand that the management of the Python heap is " "performed by the interpreter itself and that the user has no control over " "it, even if they regularly manipulate object pointers to memory blocks " "inside that heap. The allocation of heap space for Python objects and other " "internal buffers is performed on demand by the Python memory manager through " "the Python/C API functions listed in this document." msgstr "" #: ../../c-api/memory.rst:49 msgid "" "To avoid memory corruption, extension writers should never try to operate on " "Python objects with the functions exported by the C library: :c:func:" "`malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`. This will " "result in mixed calls between the C allocator and the Python memory manager " "with fatal consequences, because they implement different algorithms and " "operate on different heaps. However, one may safely allocate and release " "memory blocks with the C library allocator for individual purposes, as shown " "in the following example::" msgstr "" #: ../../c-api/memory.rst:68 msgid "" "In this example, the memory request for the I/O buffer is handled by the C " "library allocator. The Python memory manager is involved only in the " "allocation of the bytes object returned as a result." msgstr "" #: ../../c-api/memory.rst:72 msgid "" "In most situations, however, it is recommended to allocate memory from the " "Python heap specifically because the latter is under control of the Python " "memory manager. For example, this is required when the interpreter is " "extended with new object types written in C. Another reason for using the " "Python heap is the desire to *inform* the Python memory manager about the " "memory needs of the extension module. Even when the requested memory is used " "exclusively for internal, highly specific purposes, delegating all memory " "requests to the Python memory manager causes the interpreter to have a more " "accurate image of its memory footprint as a whole. Consequently, under " "certain circumstances, the Python memory manager may or may not trigger " "appropriate actions, like garbage collection, memory compaction or other " "preventive procedures. Note that by using the C library allocator as shown " "in the previous example, the allocated memory for the I/O buffer escapes " "completely the Python memory manager." msgstr "" #: ../../c-api/memory.rst:88 msgid "" "The :envvar:`PYTHONMALLOC` environment variable can be used to configure the " "memory allocators used by Python." msgstr "" #: ../../c-api/memory.rst:91 msgid "" "The :envvar:`PYTHONMALLOCSTATS` environment variable can be used to print " "statistics of the :ref:`pymalloc memory allocator ` every time a " "new pymalloc object arena is created, and on shutdown." msgstr "" #: ../../c-api/memory.rst:96 msgid "Allocator Domains" msgstr "" #: ../../c-api/memory.rst:100 msgid "" "All allocating functions belong to one of three different \"domains\" (see " "also :c:type:`PyMemAllocatorDomain`). These domains represent different " "allocation strategies and are optimized for different purposes. The specific " "details on how every domain allocates memory or what internal functions each " "domain calls is considered an implementation detail, but for debugging " "purposes a simplified table can be found at :ref:`here `. There is no hard requirement to use the memory returned by the " "allocation functions belonging to a given domain for only the purposes " "hinted by that domain (although this is the recommended practice). For " "example, one could use the memory returned by :c:func:`PyMem_RawMalloc` for " "allocating Python objects or the memory returned by :c:func:" "`PyObject_Malloc` for allocating memory for buffers." msgstr "" #: ../../c-api/memory.rst:112 msgid "The three allocation domains are:" msgstr "" #: ../../c-api/memory.rst:114 msgid "" "Raw domain: intended for allocating memory for general-purpose memory " "buffers where the allocation *must* go to the system allocator or where the " "allocator can operate without the :term:`GIL`. The memory is requested " "directly to the system." msgstr "" #: ../../c-api/memory.rst:119 msgid "" "\"Mem\" domain: intended for allocating memory for Python buffers and " "general-purpose memory buffers where the allocation must be performed with " "the :term:`GIL` held. The memory is taken from the Python private heap." msgstr "" #: ../../c-api/memory.rst:123 msgid "" "Object domain: intended for allocating memory belonging to Python objects. " "The memory is taken from the Python private heap." msgstr "" #: ../../c-api/memory.rst:126 msgid "" "When freeing memory previously allocated by the allocating functions " "belonging to a given domain,the matching specific deallocating functions " "must be used. For example, :c:func:`PyMem_Free` must be used to free memory " "allocated using :c:func:`PyMem_Malloc`." msgstr "" #: ../../c-api/memory.rst:131 msgid "Raw Memory Interface" msgstr "" #: ../../c-api/memory.rst:133 msgid "" "The following function sets are wrappers to the system allocator. These " "functions are thread-safe, the :term:`GIL ` does " "not need to be held." msgstr "" #: ../../c-api/memory.rst:137 msgid "" "The :ref:`default raw memory allocator ` uses the " "following functions: :c:func:`malloc`, :c:func:`calloc`, :c:func:`realloc` " "and :c:func:`!free`; call ``malloc(1)`` (or ``calloc(1, 1)``) when " "requesting zero bytes." msgstr "" #: ../../c-api/memory.rst:146 ../../c-api/memory.rst:217 #: ../../c-api/memory.rst:325 msgid "" "Allocates *n* bytes and returns a pointer of type :c:expr:`void*` to the " "allocated memory, or ``NULL`` if the request fails." msgstr "" #: ../../c-api/memory.rst:149 msgid "" "Requesting zero bytes returns a distinct non-``NULL`` pointer if possible, " "as if ``PyMem_RawMalloc(1)`` had been called instead. The memory will not " "have been initialized in any way." msgstr "" #: ../../c-api/memory.rst:156 ../../c-api/memory.rst:227 #: ../../c-api/memory.rst:335 msgid "" "Allocates *nelem* elements each whose size in bytes is *elsize* and returns " "a pointer of type :c:expr:`void*` to the allocated memory, or ``NULL`` if " "the request fails. The memory is initialized to zeros." msgstr "" #: ../../c-api/memory.rst:160 msgid "" "Requesting zero elements or elements of size zero bytes returns a distinct " "non-``NULL`` pointer if possible, as if ``PyMem_RawCalloc(1, 1)`` had been " "called instead." msgstr "" #: ../../c-api/memory.rst:169 ../../c-api/memory.rst:240 #: ../../c-api/memory.rst:348 msgid "" "Resizes the memory block pointed to by *p* to *n* bytes. The contents will " "be unchanged to the minimum of the old and the new sizes." msgstr "" #: ../../c-api/memory.rst:172 msgid "" "If *p* is ``NULL``, the call is equivalent to ``PyMem_RawMalloc(n)``; else " "if *n* is equal to zero, the memory block is resized but is not freed, and " "the returned pointer is non-``NULL``." msgstr "" #: ../../c-api/memory.rst:176 msgid "" "Unless *p* is ``NULL``, it must have been returned by a previous call to :c:" "func:`PyMem_RawMalloc`, :c:func:`PyMem_RawRealloc` or :c:func:" "`PyMem_RawCalloc`." msgstr "" #: ../../c-api/memory.rst:180 msgid "" "If the request fails, :c:func:`PyMem_RawRealloc` returns ``NULL`` and *p* " "remains a valid pointer to the previous memory area." msgstr "" #: ../../c-api/memory.rst:186 msgid "" "Frees the memory block pointed to by *p*, which must have been returned by a " "previous call to :c:func:`PyMem_RawMalloc`, :c:func:`PyMem_RawRealloc` or :c:" "func:`PyMem_RawCalloc`. Otherwise, or if ``PyMem_RawFree(p)`` has been " "called before, undefined behavior occurs." msgstr "" #: ../../c-api/memory.rst:191 ../../c-api/memory.rst:261 #: ../../c-api/memory.rst:369 msgid "If *p* is ``NULL``, no operation is performed." msgstr "" #: ../../c-api/memory.rst:197 msgid "Memory Interface" msgstr "" #: ../../c-api/memory.rst:199 ../../c-api/memory.rst:305 msgid "" "The following function sets, modeled after the ANSI C standard, but " "specifying behavior when requesting zero bytes, are available for allocating " "and releasing memory from the Python heap." msgstr "" #: ../../c-api/memory.rst:203 msgid "" "The :ref:`default memory allocator ` uses the :" "ref:`pymalloc memory allocator `." msgstr "" #: ../../c-api/memory.rst:208 ../../c-api/memory.rst:320 msgid "" "The :term:`GIL ` must be held when using these " "functions." msgstr "" #: ../../c-api/memory.rst:213 msgid "" "The default allocator is now pymalloc instead of system :c:func:`malloc`." msgstr "" #: ../../c-api/memory.rst:220 msgid "" "Requesting zero bytes returns a distinct non-``NULL`` pointer if possible, " "as if ``PyMem_Malloc(1)`` had been called instead. The memory will not have " "been initialized in any way." msgstr "" #: ../../c-api/memory.rst:231 msgid "" "Requesting zero elements or elements of size zero bytes returns a distinct " "non-``NULL`` pointer if possible, as if ``PyMem_Calloc(1, 1)`` had been " "called instead." msgstr "" #: ../../c-api/memory.rst:243 msgid "" "If *p* is ``NULL``, the call is equivalent to ``PyMem_Malloc(n)``; else if " "*n* is equal to zero, the memory block is resized but is not freed, and the " "returned pointer is non-``NULL``." msgstr "" #: ../../c-api/memory.rst:247 msgid "" "Unless *p* is ``NULL``, it must have been returned by a previous call to :c:" "func:`PyMem_Malloc`, :c:func:`PyMem_Realloc` or :c:func:`PyMem_Calloc`." msgstr "" #: ../../c-api/memory.rst:250 msgid "" "If the request fails, :c:func:`PyMem_Realloc` returns ``NULL`` and *p* " "remains a valid pointer to the previous memory area." msgstr "" #: ../../c-api/memory.rst:256 msgid "" "Frees the memory block pointed to by *p*, which must have been returned by a " "previous call to :c:func:`PyMem_Malloc`, :c:func:`PyMem_Realloc` or :c:func:" "`PyMem_Calloc`. Otherwise, or if ``PyMem_Free(p)`` has been called before, " "undefined behavior occurs." msgstr "" #: ../../c-api/memory.rst:263 msgid "" "The following type-oriented macros are provided for convenience. Note that " "*TYPE* refers to any C type." msgstr "" #: ../../c-api/memory.rst:269 msgid "" "Same as :c:func:`PyMem_Malloc`, but allocates ``(n * sizeof(TYPE))`` bytes " "of memory. Returns a pointer cast to :c:expr:`TYPE*`. The memory will not " "have been initialized in any way." msgstr "" #: ../../c-api/memory.rst:276 msgid "" "Same as :c:func:`PyMem_Realloc`, but the memory block is resized to ``(n * " "sizeof(TYPE))`` bytes. Returns a pointer cast to :c:expr:`TYPE*`. On " "return, *p* will be a pointer to the new memory area, or ``NULL`` in the " "event of failure." msgstr "" #: ../../c-api/memory.rst:281 msgid "" "This is a C preprocessor macro; *p* is always reassigned. Save the original " "value of *p* to avoid losing memory when handling errors." msgstr "" #: ../../c-api/memory.rst:287 msgid "Same as :c:func:`PyMem_Free`." msgstr "和 :c:func:`PyMem_Free` 相同。" #: ../../c-api/memory.rst:289 msgid "" "In addition, the following macro sets are provided for calling the Python " "memory allocator directly, without involving the C API functions listed " "above. However, note that their use does not preserve binary compatibility " "across Python versions and is therefore deprecated in extension modules." msgstr "" #: ../../c-api/memory.rst:294 msgid "``PyMem_MALLOC(size)``" msgstr "``PyMem_MALLOC(size)``" #: ../../c-api/memory.rst:295 msgid "``PyMem_NEW(type, size)``" msgstr "``PyMem_NEW(type, size)``" #: ../../c-api/memory.rst:296 msgid "``PyMem_REALLOC(ptr, size)``" msgstr "``PyMem_REALLOC(ptr, size)``" #: ../../c-api/memory.rst:297 msgid "``PyMem_RESIZE(ptr, type, size)``" msgstr "``PyMem_RESIZE(ptr, type, size)``" #: ../../c-api/memory.rst:298 msgid "``PyMem_FREE(ptr)``" msgstr "``PyMem_FREE(ptr)``" #: ../../c-api/memory.rst:299 msgid "``PyMem_DEL(ptr)``" msgstr "``PyMem_DEL(ptr)``" #: ../../c-api/memory.rst:303 msgid "Object allocators" msgstr "" #: ../../c-api/memory.rst:310 msgid "" "There is no guarantee that the memory returned by these allocators can be " "successfully cast to a Python object when intercepting the allocating " "functions in this domain by the methods described in the :ref:`Customize " "Memory Allocators ` section." msgstr "" #: ../../c-api/memory.rst:315 msgid "" "The :ref:`default object allocator ` uses the :" "ref:`pymalloc memory allocator `." msgstr "" #: ../../c-api/memory.rst:328 msgid "" "Requesting zero bytes returns a distinct non-``NULL`` pointer if possible, " "as if ``PyObject_Malloc(1)`` had been called instead. The memory will not " "have been initialized in any way." msgstr "" #: ../../c-api/memory.rst:339 msgid "" "Requesting zero elements or elements of size zero bytes returns a distinct " "non-``NULL`` pointer if possible, as if ``PyObject_Calloc(1, 1)`` had been " "called instead." msgstr "" #: ../../c-api/memory.rst:351 msgid "" "If *p* is ``NULL``, the call is equivalent to ``PyObject_Malloc(n)``; else " "if *n* is equal to zero, the memory block is resized but is not freed, and " "the returned pointer is non-``NULL``." msgstr "" #: ../../c-api/memory.rst:355 msgid "" "Unless *p* is ``NULL``, it must have been returned by a previous call to :c:" "func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or :c:func:" "`PyObject_Calloc`." msgstr "" #: ../../c-api/memory.rst:358 msgid "" "If the request fails, :c:func:`PyObject_Realloc` returns ``NULL`` and *p* " "remains a valid pointer to the previous memory area." msgstr "" #: ../../c-api/memory.rst:364 msgid "" "Frees the memory block pointed to by *p*, which must have been returned by a " "previous call to :c:func:`PyObject_Malloc`, :c:func:`PyObject_Realloc` or :c:" "func:`PyObject_Calloc`. Otherwise, or if ``PyObject_Free(p)`` has been " "called before, undefined behavior occurs." msgstr "" #: ../../c-api/memory.rst:375 msgid "Default Memory Allocators" msgstr "" #: ../../c-api/memory.rst:377 msgid "Default memory allocators:" msgstr "" #: ../../c-api/memory.rst:380 msgid "Configuration" msgstr "" #: ../../c-api/memory.rst:380 msgid "Name" msgstr "" #: ../../c-api/memory.rst:380 msgid "PyMem_RawMalloc" msgstr "PyMem_RawMalloc" #: ../../c-api/memory.rst:380 msgid "PyMem_Malloc" msgstr "PyMem_Malloc" #: ../../c-api/memory.rst:380 msgid "PyObject_Malloc" msgstr "PyObject_Malloc" #: ../../c-api/memory.rst:382 msgid "Release build" msgstr "" #: ../../c-api/memory.rst:382 msgid "``\"pymalloc\"``" msgstr "``\"pymalloc\"``" #: ../../c-api/memory.rst:382 ../../c-api/memory.rst:384 msgid "``malloc``" msgstr "``malloc``" #: ../../c-api/memory.rst:382 msgid "``pymalloc``" msgstr "``pymalloc``" #: ../../c-api/memory.rst:383 msgid "Debug build" msgstr "" #: ../../c-api/memory.rst:383 msgid "``\"pymalloc_debug\"``" msgstr "``\"pymalloc_debug\"``" #: ../../c-api/memory.rst:383 ../../c-api/memory.rst:385 msgid "``malloc`` + debug" msgstr "" #: ../../c-api/memory.rst:383 msgid "``pymalloc`` + debug" msgstr "" #: ../../c-api/memory.rst:384 msgid "Release build, without pymalloc" msgstr "" #: ../../c-api/memory.rst:384 msgid "``\"malloc\"``" msgstr "``\"malloc\"``" #: ../../c-api/memory.rst:385 msgid "Debug build, without pymalloc" msgstr "" #: ../../c-api/memory.rst:385 msgid "``\"malloc_debug\"``" msgstr "``\"malloc_debug\"``" #: ../../c-api/memory.rst:388 msgid "Legend:" msgstr "" #: ../../c-api/memory.rst:390 msgid "Name: value for :envvar:`PYTHONMALLOC` environment variable." msgstr "" #: ../../c-api/memory.rst:391 msgid "" "``malloc``: system allocators from the standard C library, C functions: :c:" "func:`malloc`, :c:func:`calloc`, :c:func:`realloc` and :c:func:`free`." msgstr "" #: ../../c-api/memory.rst:393 msgid "``pymalloc``: :ref:`pymalloc memory allocator `." msgstr "" #: ../../c-api/memory.rst:394 msgid "" "\"+ debug\": with :ref:`debug hooks on the Python memory allocators `." msgstr "" #: ../../c-api/memory.rst:396 msgid "\"Debug build\": :ref:`Python build in debug mode `." msgstr "" #: ../../c-api/memory.rst:401 msgid "Customize Memory Allocators" msgstr "" #: ../../c-api/memory.rst:407 msgid "" "Structure used to describe a memory block allocator. The structure has the " "following fields:" msgstr "" #: ../../c-api/memory.rst:411 ../../c-api/memory.rst:657 msgid "Field" msgstr "" #: ../../c-api/memory.rst:411 ../../c-api/memory.rst:657 msgid "Meaning" msgstr "" #: ../../c-api/memory.rst:413 ../../c-api/memory.rst:659 msgid "``void *ctx``" msgstr "``void *ctx``" #: ../../c-api/memory.rst:413 ../../c-api/memory.rst:659 msgid "user context passed as first argument" msgstr "" #: ../../c-api/memory.rst:415 msgid "``void* malloc(void *ctx, size_t size)``" msgstr "``void* malloc(void *ctx, size_t size)``" #: ../../c-api/memory.rst:415 msgid "allocate a memory block" msgstr "" #: ../../c-api/memory.rst:417 msgid "``void* calloc(void *ctx, size_t nelem, size_t elsize)``" msgstr "``void* calloc(void *ctx, size_t nelem, size_t elsize)``" #: ../../c-api/memory.rst:417 msgid "allocate a memory block initialized with zeros" msgstr "" #: ../../c-api/memory.rst:420 msgid "``void* realloc(void *ctx, void *ptr, size_t new_size)``" msgstr "``void* realloc(void *ctx, void *ptr, size_t new_size)``" #: ../../c-api/memory.rst:420 msgid "allocate or resize a memory block" msgstr "" #: ../../c-api/memory.rst:422 msgid "``void free(void *ctx, void *ptr)``" msgstr "``void free(void *ctx, void *ptr)``" #: ../../c-api/memory.rst:422 msgid "free a memory block" msgstr "" #: ../../c-api/memory.rst:425 msgid "" "The :c:type:`!PyMemAllocator` structure was renamed to :c:type:" "`PyMemAllocatorEx` and a new ``calloc`` field was added." msgstr "" #: ../../c-api/memory.rst:432 msgid "Enum used to identify an allocator domain. Domains:" msgstr "" #: ../../c-api/memory.rst:438 ../../c-api/memory.rst:447 #: ../../c-api/memory.rst:456 msgid "Functions:" msgstr "函式：" #: ../../c-api/memory.rst:440 msgid ":c:func:`PyMem_RawMalloc`" msgstr ":c:func:`PyMem_RawMalloc`" #: ../../c-api/memory.rst:441 msgid ":c:func:`PyMem_RawRealloc`" msgstr ":c:func:`PyMem_RawRealloc`" #: ../../c-api/memory.rst:442 msgid ":c:func:`PyMem_RawCalloc`" msgstr ":c:func:`PyMem_RawCalloc`" #: ../../c-api/memory.rst:443 msgid ":c:func:`PyMem_RawFree`" msgstr ":c:func:`PyMem_RawFree`" #: ../../c-api/memory.rst:449 msgid ":c:func:`PyMem_Malloc`," msgstr ":c:func:`PyMem_Malloc`," #: ../../c-api/memory.rst:450 msgid ":c:func:`PyMem_Realloc`" msgstr ":c:func:`PyMem_Realloc`" #: ../../c-api/memory.rst:451 msgid ":c:func:`PyMem_Calloc`" msgstr ":c:func:`PyMem_Calloc`" #: ../../c-api/memory.rst:452 msgid ":c:func:`PyMem_Free`" msgstr ":c:func:`PyMem_Free`" #: ../../c-api/memory.rst:458 msgid ":c:func:`PyObject_Malloc`" msgstr ":c:func:`PyObject_Malloc`" #: ../../c-api/memory.rst:459 msgid ":c:func:`PyObject_Realloc`" msgstr ":c:func:`PyObject_Realloc`" #: ../../c-api/memory.rst:460 msgid ":c:func:`PyObject_Calloc`" msgstr ":c:func:`PyObject_Calloc`" #: ../../c-api/memory.rst:461 msgid ":c:func:`PyObject_Free`" msgstr ":c:func:`PyObject_Free`" #: ../../c-api/memory.rst:465 msgid "Get the memory block allocator of the specified domain." msgstr "" #: ../../c-api/memory.rst:470 msgid "Set the memory block allocator of the specified domain." msgstr "" #: ../../c-api/memory.rst:472 msgid "" "The new allocator must return a distinct non-``NULL`` pointer when " "requesting zero bytes." msgstr "" #: ../../c-api/memory.rst:475 msgid "" "For the :c:macro:`PYMEM_DOMAIN_RAW` domain, the allocator must be thread-" "safe: the :term:`GIL ` is not held when the " "allocator is called." msgstr "" #: ../../c-api/memory.rst:479 msgid "" "For the remaining domains, the allocator must also be thread-safe: the " "allocator may be called in different interpreters that do not share a " "``GIL``." msgstr "" #: ../../c-api/memory.rst:483 msgid "" "If the new allocator is not a hook (does not call the previous allocator), " "the :c:func:`PyMem_SetupDebugHooks` function must be called to reinstall the " "debug hooks on top on the new allocator." msgstr "" #: ../../c-api/memory.rst:487 msgid "" "See also :c:member:`PyPreConfig.allocator` and :ref:`Preinitialize Python " "with PyPreConfig `." msgstr "" #: ../../c-api/memory.rst:492 msgid ":c:func:`PyMem_SetAllocator` does have the following contract:" msgstr "" #: ../../c-api/memory.rst:494 msgid "" "It can be called after :c:func:`Py_PreInitialize` and before :c:func:" "`Py_InitializeFromConfig` to install a custom memory allocator. There are no " "restrictions over the installed allocator other than the ones imposed by the " "domain (for instance, the Raw Domain allows the allocator to be called " "without the GIL held). See :ref:`the section on allocator domains ` for more information." msgstr "" #: ../../c-api/memory.rst:502 msgid "" "If called after Python has finish initializing (after :c:func:" "`Py_InitializeFromConfig` has been called) the allocator **must** wrap the " "existing allocator. Substituting the current allocator for some other " "arbitrary one is **not supported**." msgstr "" #: ../../c-api/memory.rst:507 msgid "All allocators must be thread-safe." msgstr "" #: ../../c-api/memory.rst:513 msgid "" "Setup :ref:`debug hooks in the Python memory allocators ` " "to detect memory errors." msgstr "" #: ../../c-api/memory.rst:520 msgid "Debug hooks on the Python memory allocators" msgstr "" #: ../../c-api/memory.rst:522 msgid "" "When :ref:`Python is built in debug mode `, the :c:func:" "`PyMem_SetupDebugHooks` function is called at the :ref:`Python " "preinitialization ` to setup debug hooks on Python memory " "allocators to detect memory errors." msgstr "" #: ../../c-api/memory.rst:527 msgid "" "The :envvar:`PYTHONMALLOC` environment variable can be used to install debug " "hooks on a Python compiled in release mode (ex: ``PYTHONMALLOC=debug``)." msgstr "" #: ../../c-api/memory.rst:530 msgid "" "The :c:func:`PyMem_SetupDebugHooks` function can be used to set debug hooks " "after calling :c:func:`PyMem_SetAllocator`." msgstr "" #: ../../c-api/memory.rst:533 msgid "" "These debug hooks fill dynamically allocated memory blocks with special, " "recognizable bit patterns. Newly allocated memory is filled with the byte " "``0xCD`` (``PYMEM_CLEANBYTE``), freed memory is filled with the byte " "``0xDD`` (``PYMEM_DEADBYTE``). Memory blocks are surrounded by \"forbidden " "bytes\" filled with the byte ``0xFD`` (``PYMEM_FORBIDDENBYTE``). Strings of " "these bytes are unlikely to be valid addresses, floats, or ASCII strings." msgstr "" #: ../../c-api/memory.rst:540 msgid "Runtime checks:" msgstr "" #: ../../c-api/memory.rst:542 msgid "" "Detect API violations. For example, detect if :c:func:`PyObject_Free` is " "called on a memory block allocated by :c:func:`PyMem_Malloc`." msgstr "" #: ../../c-api/memory.rst:544 msgid "Detect write before the start of the buffer (buffer underflow)." msgstr "" #: ../../c-api/memory.rst:545 msgid "Detect write after the end of the buffer (buffer overflow)." msgstr "" #: ../../c-api/memory.rst:546 msgid "" "Check that the :term:`GIL ` is held when allocator " "functions of :c:macro:`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) " "and :c:macro:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) domains are " "called." msgstr "" #: ../../c-api/memory.rst:551 msgid "" "On error, the debug hooks use the :mod:`tracemalloc` module to get the " "traceback where a memory block was allocated. The traceback is only " "displayed if :mod:`tracemalloc` is tracing Python memory allocations and the " "memory block was traced." msgstr "" #: ../../c-api/memory.rst:556 msgid "" "Let *S* = ``sizeof(size_t)``. ``2*S`` bytes are added at each end of each " "block of *N* bytes requested. The memory layout is like so, where p " "represents the address returned by a malloc-like or realloc-like function " "(``p[i:j]`` means the slice of bytes from ``*(p+i)`` inclusive up to " "``*(p+j)`` exclusive; note that the treatment of negative indices differs " "from a Python slice):" msgstr "" #: ../../c-api/memory.rst:563 msgid "``p[-2*S:-S]``" msgstr "``p[-2*S:-S]``" #: ../../c-api/memory.rst:563 msgid "" "Number of bytes originally asked for. This is a size_t, big-endian (easier " "to read in a memory dump)." msgstr "" #: ../../c-api/memory.rst:570 msgid "``p[-S]``" msgstr "``p[-S]``" #: ../../c-api/memory.rst:566 msgid "API identifier (ASCII character):" msgstr "" #: ../../c-api/memory.rst:568 msgid "``'r'`` for :c:macro:`PYMEM_DOMAIN_RAW`." msgstr "" #: ../../c-api/memory.rst:569 msgid "``'m'`` for :c:macro:`PYMEM_DOMAIN_MEM`." msgstr "" #: ../../c-api/memory.rst:570 msgid "``'o'`` for :c:macro:`PYMEM_DOMAIN_OBJ`." msgstr "" #: ../../c-api/memory.rst:573 msgid "``p[-S+1:0]``" msgstr "``p[-S+1:0]``" #: ../../c-api/memory.rst:573 msgid "Copies of PYMEM_FORBIDDENBYTE. Used to catch under- writes and reads." msgstr "" #: ../../c-api/memory.rst:582 msgid "``p[0:N]``" msgstr "``p[0:N]``" #: ../../c-api/memory.rst:576 msgid "" "The requested memory, filled with copies of PYMEM_CLEANBYTE, used to catch " "reference to uninitialized memory. When a realloc-like function is called " "requesting a larger memory block, the new excess bytes are also filled with " "PYMEM_CLEANBYTE. When a free-like function is called, these are overwritten " "with PYMEM_DEADBYTE, to catch reference to freed memory. When a realloc- " "like function is called requesting a smaller memory block, the excess old " "bytes are also filled with PYMEM_DEADBYTE." msgstr "" #: ../../c-api/memory.rst:585 msgid "``p[N:N+S]``" msgstr "``p[N:N+S]``" #: ../../c-api/memory.rst:585 msgid "Copies of PYMEM_FORBIDDENBYTE. Used to catch over- writes and reads." msgstr "" #: ../../c-api/memory.rst:596 msgid "``p[N+S:N+2*S]``" msgstr "``p[N+S:N+2*S]``" #: ../../c-api/memory.rst:588 msgid "" "Only used if the ``PYMEM_DEBUG_SERIALNO`` macro is defined (not defined by " "default)." msgstr "" #: ../../c-api/memory.rst:591 msgid "" "A serial number, incremented by 1 on each call to a malloc-like or realloc-" "like function. Big-endian :c:type:`size_t`. If \"bad memory\" is detected " "later, the serial number gives an excellent way to set a breakpoint on the " "next run, to capture the instant at which this block was passed out. The " "static function bumpserialno() in obmalloc.c is the only place the serial " "number is incremented, and exists so you can set such a breakpoint easily." msgstr "" #: ../../c-api/memory.rst:598 msgid "" "A realloc-like or free-like function first checks that the " "PYMEM_FORBIDDENBYTE bytes at each end are intact. If they've been altered, " "diagnostic output is written to stderr, and the program is aborted via " "Py_FatalError(). The other main failure mode is provoking a memory error " "when a program reads up one of the special bit patterns and tries to use it " "as an address. If you get in a debugger then and look at the object, you're " "likely to see that it's entirely filled with PYMEM_DEADBYTE (meaning freed " "memory is getting used) or PYMEM_CLEANBYTE (meaning uninitialized memory is " "getting used)." msgstr "" #: ../../c-api/memory.rst:607 msgid "" "The :c:func:`PyMem_SetupDebugHooks` function now also works on Python " "compiled in release mode. On error, the debug hooks now use :mod:" "`tracemalloc` to get the traceback where a memory block was allocated. The " "debug hooks now also check if the GIL is held when functions of :c:macro:" "`PYMEM_DOMAIN_OBJ` and :c:macro:`PYMEM_DOMAIN_MEM` domains are called." msgstr "" #: ../../c-api/memory.rst:615 msgid "" "Byte patterns ``0xCB`` (``PYMEM_CLEANBYTE``), ``0xDB`` (``PYMEM_DEADBYTE``) " "and ``0xFB`` (``PYMEM_FORBIDDENBYTE``) have been replaced with ``0xCD``, " "``0xDD`` and ``0xFD`` to use the same values than Windows CRT debug " "``malloc()`` and ``free()``." msgstr "" #: ../../c-api/memory.rst:625 msgid "The pymalloc allocator" msgstr "" #: ../../c-api/memory.rst:627 msgid "" "Python has a *pymalloc* allocator optimized for small objects (smaller or " "equal to 512 bytes) with a short lifetime. It uses memory mappings called " "\"arenas\" with a fixed size of 256 KiB. It falls back to :c:func:" "`PyMem_RawMalloc` and :c:func:`PyMem_RawRealloc` for allocations larger than " "512 bytes." msgstr "" #: ../../c-api/memory.rst:632 msgid "" "*pymalloc* is the :ref:`default allocator ` of " "the :c:macro:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) and :c:macro:" "`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) domains." msgstr "" #: ../../c-api/memory.rst:636 msgid "The arena allocator uses the following functions:" msgstr "" #: ../../c-api/memory.rst:638 msgid ":c:func:`!VirtualAlloc` and :c:func:`!VirtualFree` on Windows," msgstr "" #: ../../c-api/memory.rst:639 msgid ":c:func:`!mmap` and :c:func:`!munmap` if available," msgstr "" #: ../../c-api/memory.rst:640 msgid ":c:func:`malloc` and :c:func:`free` otherwise." msgstr "" #: ../../c-api/memory.rst:642 msgid "" "This allocator is disabled if Python is configured with the :option:`--" "without-pymalloc` option. It can also be disabled at runtime using the :" "envvar:`PYTHONMALLOC` environment variable (ex: ``PYTHONMALLOC=malloc``)." msgstr "" #: ../../c-api/memory.rst:647 msgid "Customize pymalloc Arena Allocator" msgstr "" #: ../../c-api/memory.rst:653 msgid "" "Structure used to describe an arena allocator. The structure has three " "fields:" msgstr "" #: ../../c-api/memory.rst:661 msgid "``void* alloc(void *ctx, size_t size)``" msgstr "``void* alloc(void *ctx, size_t size)``" #: ../../c-api/memory.rst:661 msgid "allocate an arena of size bytes" msgstr "" #: ../../c-api/memory.rst:663 msgid "``void free(void *ctx, void *ptr, size_t size)``" msgstr "``void free(void *ctx, void *ptr, size_t size)``" #: ../../c-api/memory.rst:663 msgid "free an arena" msgstr "" #: ../../c-api/memory.rst:668 msgid "Get the arena allocator." msgstr "" #: ../../c-api/memory.rst:672 msgid "Set the arena allocator." msgstr "" #: ../../c-api/memory.rst:676 msgid "tracemalloc C API" msgstr "" #: ../../c-api/memory.rst:682 msgid "Track an allocated memory block in the :mod:`tracemalloc` module." msgstr "" #: ../../c-api/memory.rst:684 msgid "" "Return ``0`` on success, return ``-1`` on error (failed to allocate memory " "to store the trace). Return ``-2`` if tracemalloc is disabled." msgstr "" #: ../../c-api/memory.rst:687 msgid "If memory block is already tracked, update the existing trace." msgstr "" #: ../../c-api/memory.rst:691 msgid "" "Untrack an allocated memory block in the :mod:`tracemalloc` module. Do " "nothing if the block was not tracked." msgstr "" #: ../../c-api/memory.rst:694 msgid "Return ``-2`` if tracemalloc is disabled, otherwise return ``0``." msgstr "" #: ../../c-api/memory.rst:700 msgid "Examples" msgstr "範例" #: ../../c-api/memory.rst:702 msgid "" "Here is the example from section :ref:`memoryoverview`, rewritten so that " "the I/O buffer is allocated from the Python heap by using the first function " "set::" msgstr "" #: ../../c-api/memory.rst:715 msgid "The same code using the type-oriented function set::" msgstr "" #: ../../c-api/memory.rst:727 msgid "" "Note that in the two examples above, the buffer is always manipulated via " "functions belonging to the same set. Indeed, it is required to use the same " "memory API family for a given memory block, so that the risk of mixing " "different allocators is reduced to a minimum. The following code sequence " "contains two errors, one of which is labeled as *fatal* because it mixes two " "different allocators operating on different heaps. ::" msgstr "" #: ../../c-api/memory.rst:742 msgid "" "In addition to the functions aimed at handling raw memory blocks from the " "Python heap, objects in Python are allocated and released with :c:macro:" "`PyObject_New`, :c:macro:`PyObject_NewVar` and :c:func:`PyObject_Del`." msgstr "" #: ../../c-api/memory.rst:746 msgid "" "These will be explained in the next chapter on defining and implementing new " "object types in C." msgstr "" #: ../../c-api/memory.rst:43 msgid "malloc()" msgstr "malloc()" #: ../../c-api/memory.rst:43 msgid "calloc()" msgstr "calloc()" #: ../../c-api/memory.rst:43 msgid "realloc()" msgstr "realloc()" #: ../../c-api/memory.rst:43 msgid "free()" msgstr "free()"