44# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
55#
66# Translators:
7- # python-doc bot, 2025
7+ # python-doc bot, 2026
88#
99#, fuzzy
1010msgid ""
1111msgstr ""
1212"Project-Id-Version : Python 3.14\n "
1313"Report-Msgid-Bugs-To : \n "
14- "POT-Creation-Date : 2026-02-25 14:44 +0000\n "
14+ "POT-Creation-Date : 2026-03-15 14:24 +0000\n "
1515"PO-Revision-Date : 2025-09-16 00:00+0000\n "
16- "Last-Translator : python-doc bot, 2025 \n "
16+ "Last-Translator : python-doc bot, 2026 \n "
1717"Language-Team : Japanese (https://app.transifex.com/python-doc/teams/5390/ "
1818"ja/)\n "
1919"MIME-Version : 1.0\n "
@@ -527,21 +527,120 @@ msgid ""
527527msgstr ""
528528
529529#: ../../howto/instrumentation.rst:345
530+ msgid "C Entry Points"
531+ msgstr ""
532+
533+ #: ../../howto/instrumentation.rst:347
534+ msgid ""
535+ "To simplify triggering of DTrace markers, Python's C API comes with a number "
536+ "of helper functions that mirror each static marker. On builds of Python "
537+ "without DTrace enabled, these do nothing."
538+ msgstr ""
539+
540+ #: ../../howto/instrumentation.rst:351
541+ msgid ""
542+ "In general, it is not necessary to call these yourself, as Python will do it "
543+ "for you."
544+ msgstr ""
545+
546+ #: ../../howto/instrumentation.rst:358
547+ msgid "C API Function"
548+ msgstr ""
549+
550+ #: ../../howto/instrumentation.rst:359
551+ msgid "Static Marker"
552+ msgstr ""
553+
554+ #: ../../howto/instrumentation.rst:360
555+ msgid "Notes"
556+ msgstr "注釈"
557+
558+ #: ../../howto/instrumentation.rst:362
559+ msgid ":c:func:`!line`"
560+ msgstr ""
561+
562+ #: ../../howto/instrumentation.rst:365
563+ msgid ":c:func:`!function__entry`"
564+ msgstr ""
565+
566+ #: ../../howto/instrumentation.rst:368
567+ msgid ":c:func:`!function__return`"
568+ msgstr ""
569+
570+ #: ../../howto/instrumentation.rst:371
571+ msgid ":c:func:`!gc__start`"
572+ msgstr ""
573+
574+ #: ../../howto/instrumentation.rst:374
575+ msgid ":c:func:`!gc__done`"
576+ msgstr ""
577+
578+ #: ../../howto/instrumentation.rst:377
579+ msgid ":c:func:`!instance__new__start`"
580+ msgstr ""
581+
582+ #: ../../howto/instrumentation.rst:378 ../../howto/instrumentation.rst:381
583+ #: ../../howto/instrumentation.rst:384 ../../howto/instrumentation.rst:387
584+ msgid "Not used by Python"
585+ msgstr ""
586+
587+ #: ../../howto/instrumentation.rst:380
588+ msgid ":c:func:`!instance__new__done`"
589+ msgstr ""
590+
591+ #: ../../howto/instrumentation.rst:383
592+ msgid ":c:func:`!instance__delete__start`"
593+ msgstr ""
594+
595+ #: ../../howto/instrumentation.rst:386
596+ msgid ":c:func:`!instance__delete__done`"
597+ msgstr ""
598+
599+ #: ../../howto/instrumentation.rst:389
600+ msgid ":c:func:`!import__find__load__start`"
601+ msgstr ""
602+
603+ #: ../../howto/instrumentation.rst:392
604+ msgid ":c:func:`!import__find__load__done`"
605+ msgstr ""
606+
607+ #: ../../howto/instrumentation.rst:395
608+ msgid ":c:func:`!audit`"
609+ msgstr ""
610+
611+ #: ../../howto/instrumentation.rst:400
612+ msgid "C Probing Checks"
613+ msgstr ""
614+
615+ #: ../../howto/instrumentation.rst:415
616+ msgid ""
617+ "All calls to ``PyDTrace`` functions must be guarded by a call to one of "
618+ "these functions. This allows Python to minimize performance impact when "
619+ "probing is disabled."
620+ msgstr ""
621+
622+ #: ../../howto/instrumentation.rst:419
623+ msgid ""
624+ "On builds without DTrace enabled, these functions do nothing and return "
625+ "``0``."
626+ msgstr ""
627+
628+ #: ../../howto/instrumentation.rst:423
530629msgid "SystemTap Tapsets"
531630msgstr "SystemTap Tapset"
532631
533- #: ../../howto/instrumentation.rst:347
632+ #: ../../howto/instrumentation.rst:425
534633msgid ""
535634"The higher-level way to use the SystemTap integration is to use a "
536635"\" tapset\" : SystemTap's equivalent of a library, which hides some of the "
537636"lower-level details of the static markers."
538637msgstr ""
539638
540- #: ../../howto/instrumentation.rst:351
639+ #: ../../howto/instrumentation.rst:429
541640msgid "Here is a tapset file, based on a non-shared build of CPython:"
542641msgstr ""
543642
544- #: ../../howto/instrumentation.rst:353
643+ #: ../../howto/instrumentation.rst:431
545644msgid ""
546645"/*\n"
547646" Provide a higher-level wrapping around the function__entry and\n"
@@ -564,38 +663,38 @@ msgid ""
564663"}"
565664msgstr ""
566665
567- #: ../../howto/instrumentation.rst:374
666+ #: ../../howto/instrumentation.rst:452
568667msgid ""
569668"If this file is installed in SystemTap's tapset directory (e.g. ``/usr/share/"
570669"systemtap/tapset``), then these additional probepoints become available:"
571670msgstr ""
572671
573- #: ../../howto/instrumentation.rst:380
672+ #: ../../howto/instrumentation.rst:458
574673msgid ""
575674"This probe point indicates that execution of a Python function has begun. It "
576675"is only triggered for pure-Python (bytecode) functions."
577676msgstr ""
578677
579- #: ../../howto/instrumentation.rst:385
678+ #: ../../howto/instrumentation.rst:463
580679msgid ""
581680"This probe point is the converse of ``python.function.return``, and "
582681"indicates that execution of a Python function has ended (either via "
583682"``return``, or via an exception). It is only triggered for pure-Python "
584683"(bytecode) functions."
585684msgstr ""
586685
587- #: ../../howto/instrumentation.rst:392
686+ #: ../../howto/instrumentation.rst:470
588687msgid "Examples"
589688msgstr "使用例"
590689
591- #: ../../howto/instrumentation.rst:393
690+ #: ../../howto/instrumentation.rst:471
592691msgid ""
593692"This SystemTap script uses the tapset above to more cleanly implement the "
594693"example given above of tracing the Python function-call hierarchy, without "
595694"needing to directly name the static markers:"
596695msgstr ""
597696
598- #: ../../howto/instrumentation.rst:397
697+ #: ../../howto/instrumentation.rst:475
599698msgid ""
600699"probe python.function.entry\n"
601700"{\n"
@@ -610,14 +709,14 @@ msgid ""
610709"}"
611710msgstr ""
612711
613- #: ../../howto/instrumentation.rst:412
712+ #: ../../howto/instrumentation.rst:490
614713msgid ""
615714"The following script uses the tapset above to provide a top-like view of all "
616715"running CPython code, showing the top 20 most frequently entered bytecode "
617716"frames, each second, across the whole system:"
618717msgstr ""
619718
620- #: ../../howto/instrumentation.rst:416
719+ #: ../../howto/instrumentation.rst:494
621720msgid ""
622721"global fn_calls;\n"
623722"\n"
0 commit comments