@@ -17,7 +17,7 @@ msgid ""
17
17
msgstr ""
18
18
"Project-Id-Version : Python 3.7\n "
19
19
"Report-Msgid-Bugs-To : \n "
20
- "POT-Creation-Date : 2019-01-01 10:14 +0900\n "
20
+ "POT-Creation-Date : 2019-04-12 11:10 +0900\n "
21
21
"PO-Revision-Date : 2017-02-16 17:37+0000\n "
22
22
"Last-Translator : tomo, 2018\n "
23
23
"Language-Team : Japanese (https://www.transifex.com/python-doc/teams/5390/ja/)\n "
@@ -567,19 +567,19 @@ msgid ""
567
567
"fields:"
568
568
msgstr "メモリブロックアロケータを記述するための構造体です。4つのフィールドを持ちます:"
569
569
570
- #: ../../c-api/memory.rst:368 ../../c-api/memory.rst:506
570
+ #: ../../c-api/memory.rst:368 ../../c-api/memory.rst:513
571
571
msgid "Field"
572
572
msgstr "フィールド"
573
573
574
- #: ../../c-api/memory.rst:368 ../../c-api/memory.rst:506
574
+ #: ../../c-api/memory.rst:368 ../../c-api/memory.rst:513
575
575
msgid "Meaning"
576
576
msgstr "意味"
577
577
578
- #: ../../c-api/memory.rst:370 ../../c-api/memory.rst:508
578
+ #: ../../c-api/memory.rst:370 ../../c-api/memory.rst:515
579
579
msgid "``void *ctx``"
580
580
msgstr "``void *ctx``"
581
581
582
- #: ../../c-api/memory.rst:370 ../../c-api/memory.rst:508
582
+ #: ../../c-api/memory.rst:370 ../../c-api/memory.rst:515
583
583
msgid "user context passed as first argument"
584
584
msgstr "第一引数として渡されるユーザコンテクスト"
585
585
@@ -718,54 +718,55 @@ msgstr "Python メモリアロケータ関数のバグを検出するための
718
718
719
719
#: ../../c-api/memory.rst:443
720
720
msgid ""
721
- "Newly allocated memory is filled with the byte ``0xCB``, freed memory is "
722
- "filled with the byte ``0xDB``."
723
- msgstr "新たに割り当てられたメモリはバイト ``0xCB`` で埋められ、解放されたメモリはバイト ``0xDB`` で埋められます。"
721
+ "Newly allocated memory is filled with the byte ``0xCD`` (``CLEANBYTE``), "
722
+ "freed memory is filled with the byte ``0xDD`` (``DEADBYTE``). Memory blocks "
723
+ "are surrounded by \" forbidden bytes\" (``FORBIDDENBYTE``: byte ``0xFD``)."
724
+ msgstr ""
724
725
725
- #: ../../c-api/memory.rst:446
726
+ #: ../../c-api/memory.rst:447
726
727
msgid "Runtime checks:"
727
728
msgstr "実行時チェック:"
728
729
729
- #: ../../c-api/memory.rst:448
730
+ #: ../../c-api/memory.rst:449
730
731
msgid ""
731
732
"Detect API violations, ex: :c:func:`PyObject_Free` called on a buffer "
732
733
"allocated by :c:func:`PyMem_Malloc`"
733
734
msgstr ""
734
735
"API 違反を検出します。例: :c:func:`PyMem_Malloc` が割り当てたバッファに対して "
735
736
":c:func:`PyObject_Free` を呼びだした。"
736
737
737
- #: ../../c-api/memory.rst:450
738
+ #: ../../c-api/memory.rst:451
738
739
msgid "Detect write before the start of the buffer (buffer underflow)"
739
740
msgstr "バッファの開始前の書き込み (バッファアンダーフロー) を検出します"
740
741
741
- #: ../../c-api/memory.rst:451
742
+ #: ../../c-api/memory.rst:452
742
743
msgid "Detect write after the end of the buffer (buffer overflow)"
743
744
msgstr "バッファ終了後の書き込み (バッファオーバーフロー) を検出します"
744
745
745
- #: ../../c-api/memory.rst:452
746
+ #: ../../c-api/memory.rst:453
746
747
msgid ""
747
748
"Check that the :term:`GIL <global interpreter lock>` is held when allocator "
748
749
"functions of :c:data:`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) and "
749
750
":c:data:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) domains are called"
750
751
msgstr ""
751
752
752
- #: ../../c-api/memory.rst:457
753
+ #: ../../c-api/memory.rst:458
753
754
msgid ""
754
755
"On error, the debug hooks use the :mod:`tracemalloc` module to get the "
755
756
"traceback where a memory block was allocated. The traceback is only "
756
757
"displayed if :mod:`tracemalloc` is tracing Python memory allocations and the"
757
758
" memory block was traced."
758
759
msgstr ""
759
760
760
- #: ../../c-api/memory.rst:462
761
+ #: ../../c-api/memory.rst:463
761
762
msgid ""
762
763
"These hooks are :ref:`installed by default <default-memory-allocators>` if "
763
764
"Python is compiled in debug mode. The :envvar:`PYTHONMALLOC` environment "
764
765
"variable can be used to install debug hooks on a Python compiled in release "
765
766
"mode."
766
767
msgstr ""
767
768
768
- #: ../../c-api/memory.rst:467
769
+ #: ../../c-api/memory.rst:468
769
770
msgid ""
770
771
"This function now also works on Python compiled in release mode. On error, "
771
772
"the debug hooks now use :mod:`tracemalloc` to get the traceback where a "
@@ -774,11 +775,18 @@ msgid ""
774
775
":c:data:`PYMEM_DOMAIN_MEM` domains are called."
775
776
msgstr ""
776
777
777
- #: ../../c-api/memory.rst:478
778
+ #: ../../c-api/memory.rst:475
779
+ msgid ""
780
+ "Byte patterns ``0xCB`` (``CLEANBYTE``), ``0xDB`` (``DEADBYTE``) and ``0xFB``"
781
+ " (``FORBIDDENBYTE``) have been replaced with ``0xCD``, ``0xDD`` and ``0xFD``"
782
+ " to use the same values than Windows CRT debug ``malloc()`` and ``free()``."
783
+ msgstr ""
784
+
785
+ #: ../../c-api/memory.rst:485
778
786
msgid "The pymalloc allocator"
779
787
msgstr "pymalloc アロケータ"
780
788
781
- #: ../../c-api/memory.rst:480
789
+ #: ../../c-api/memory.rst:487
782
790
msgid ""
783
791
"Python has a *pymalloc* allocator optimized for small objects (smaller or "
784
792
"equal to 512 bytes) with a short lifetime. It uses memory mappings called "
@@ -787,72 +795,72 @@ msgid ""
787
795
"larger than 512 bytes."
788
796
msgstr ""
789
797
790
- #: ../../c-api/memory.rst:485
798
+ #: ../../c-api/memory.rst:492
791
799
msgid ""
792
800
"*pymalloc* is the :ref:`default allocator <default-memory-allocators>` of "
793
801
"the :c:data:`PYMEM_DOMAIN_MEM` (ex: :c:func:`PyMem_Malloc`) and "
794
802
":c:data:`PYMEM_DOMAIN_OBJ` (ex: :c:func:`PyObject_Malloc`) domains."
795
803
msgstr ""
796
804
797
- #: ../../c-api/memory.rst:489
805
+ #: ../../c-api/memory.rst:496
798
806
msgid "The arena allocator uses the following functions:"
799
807
msgstr "アリーナアロケータは、次の関数を使います:"
800
808
801
- #: ../../c-api/memory.rst:491
809
+ #: ../../c-api/memory.rst:498
802
810
msgid ":c:func:`VirtualAlloc` and :c:func:`VirtualFree` on Windows,"
803
811
msgstr "Windows では :c:func:`VirtualAlloc` と :c:func:`VirtualFree`、"
804
812
805
- #: ../../c-api/memory.rst:492
813
+ #: ../../c-api/memory.rst:499
806
814
msgid ":c:func:`mmap` and :c:func:`munmap` if available,"
807
815
msgstr "利用できる場合、:c:func:`mmap` と :c:func:`munmap`、"
808
816
809
- #: ../../c-api/memory.rst:493
817
+ #: ../../c-api/memory.rst:500
810
818
msgid ":c:func:`malloc` and :c:func:`free` otherwise."
811
819
msgstr "それ以外の場合は :c:func:`malloc` と :c:func:`free`。"
812
820
813
- #: ../../c-api/memory.rst:496
821
+ #: ../../c-api/memory.rst:503
814
822
msgid "Customize pymalloc Arena Allocator"
815
823
msgstr "pymalloc アリーナアロケータのカスタマイズ"
816
824
817
- #: ../../c-api/memory.rst:502
825
+ #: ../../c-api/memory.rst:509
818
826
msgid ""
819
827
"Structure used to describe an arena allocator. The structure has three "
820
828
"fields:"
821
829
msgstr "アリーナアロケータを記述するための構造体です。3つのフィールドを持ちます:"
822
830
823
- #: ../../c-api/memory.rst:510
831
+ #: ../../c-api/memory.rst:517
824
832
msgid "``void* alloc(void *ctx, size_t size)``"
825
833
msgstr "``void* alloc(void *ctx, size_t size)``"
826
834
827
- #: ../../c-api/memory.rst:510
835
+ #: ../../c-api/memory.rst:517
828
836
msgid "allocate an arena of size bytes"
829
837
msgstr "size バイトのアリーナを割り当てます"
830
838
831
- #: ../../c-api/memory.rst:512
839
+ #: ../../c-api/memory.rst:519
832
840
msgid "``void free(void *ctx, size_t size, void *ptr)``"
833
841
msgstr "``void free(void *ctx, size_t size, void *ptr)``"
834
842
835
- #: ../../c-api/memory.rst:512
843
+ #: ../../c-api/memory.rst:519
836
844
msgid "free an arena"
837
845
msgstr "アリーナを解放します"
838
846
839
- #: ../../c-api/memory.rst:517
847
+ #: ../../c-api/memory.rst:524
840
848
msgid "Get the arena allocator."
841
849
msgstr "アリーナアロケータを取得します。"
842
850
843
- #: ../../c-api/memory.rst:521
851
+ #: ../../c-api/memory.rst:528
844
852
msgid "Set the arena allocator."
845
853
msgstr "アリーナアロケータを設定します。"
846
854
847
- #: ../../c-api/memory.rst:525
855
+ #: ../../c-api/memory.rst:532
848
856
msgid "tracemalloc C API"
849
857
msgstr ""
850
858
851
- #: ../../c-api/memory.rst:549
859
+ #: ../../c-api/memory.rst:556
852
860
msgid "Examples"
853
861
msgstr "使用例"
854
862
855
- #: ../../c-api/memory.rst:551
863
+ #: ../../c-api/memory.rst:558
856
864
msgid ""
857
865
"Here is the example from section :ref:`memoryoverview`, rewritten so that "
858
866
"the I/O buffer is allocated from the Python heap by using the first function"
@@ -861,11 +869,11 @@ msgstr ""
861
869
"最初に述べた関数セットを使って、 :ref:`memoryoverview` 節の例を Python ヒープに I/O "
862
870
"バッファをメモリ確保するように書き換えたものを以下に示します::"
863
871
864
- #: ../../c-api/memory.rst:564
872
+ #: ../../c-api/memory.rst:571
865
873
msgid "The same code using the type-oriented function set::"
866
874
msgstr "同じコードを型対象の関数セットで書いたものを以下に示します::"
867
875
868
- #: ../../c-api/memory.rst:576
876
+ #: ../../c-api/memory.rst:583
869
877
msgid ""
870
878
"Note that in the two examples above, the buffer is always manipulated via "
871
879
"functions belonging to the same set. Indeed, it is required to use the same "
@@ -879,7 +887,7 @@ msgstr ""
879
887
"ファミリを使って行うことが必要です。以下のコードには二つのエラーがあり、そのうちの一つには異なるヒープを操作する別のメモリ操作関数を混用しているので "
880
888
"*致命的 (Fatal)* とラベルづけをしています。 ::"
881
889
882
- #: ../../c-api/memory.rst:591
890
+ #: ../../c-api/memory.rst:598
883
891
msgid ""
884
892
"In addition to the functions aimed at handling raw memory blocks from the "
885
893
"Python heap, objects in Python are allocated and released with "
@@ -890,7 +898,7 @@ msgstr ""
890
898
":c:func:`PyObject_NewVar` 、および :c:func:`PyObject_Del` を使うと、 Python "
891
899
"におけるオブジェクトをメモリ確保したり解放したりできます。"
892
900
893
- #: ../../c-api/memory.rst:595
901
+ #: ../../c-api/memory.rst:602
894
902
msgid ""
895
903
"These will be explained in the next chapter on defining and implementing new"
896
904
" object types in C."
0 commit comments