-
-
Notifications
You must be signed in to change notification settings - Fork 16
/
Copy pathinstrumentation.po
601 lines (524 loc) · 18.1 KB
/
instrumentation.po
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
# 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.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3.12\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-02-17 21:03+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: howto/instrumentation.rst:7
msgid "Instrumenting CPython with DTrace and SystemTap"
msgstr ""
#: howto/instrumentation.rst:0
msgid "author"
msgstr ""
#: howto/instrumentation.rst:9
msgid "David Malcolm"
msgstr ""
#: howto/instrumentation.rst:10
msgid "Łukasz Langa"
msgstr ""
#: howto/instrumentation.rst:12
msgid ""
"DTrace and SystemTap are monitoring tools, each providing a way to inspect "
"what the processes on a computer system are doing. They both use domain-"
"specific languages allowing a user to write scripts which:"
msgstr ""
#: howto/instrumentation.rst:16
msgid "filter which processes are to be observed"
msgstr ""
#: howto/instrumentation.rst:17
msgid "gather data from the processes of interest"
msgstr ""
#: howto/instrumentation.rst:18
msgid "generate reports on the data"
msgstr ""
#: howto/instrumentation.rst:20
msgid ""
"As of Python 3.6, CPython can be built with embedded \"markers\", also known "
"as \"probes\", that can be observed by a DTrace or SystemTap script, making "
"it easier to monitor what the CPython processes on a system are doing."
msgstr ""
#: howto/instrumentation.rst:27
msgid ""
"DTrace markers are implementation details of the CPython interpreter. No "
"guarantees are made about probe compatibility between versions of CPython. "
"DTrace scripts can stop working or work incorrectly without warning when "
"changing CPython versions."
msgstr ""
#: howto/instrumentation.rst:34
msgid "Enabling the static markers"
msgstr ""
#: howto/instrumentation.rst:36
msgid ""
"macOS comes with built-in support for DTrace. On Linux, in order to build "
"CPython with the embedded markers for SystemTap, the SystemTap development "
"tools must be installed."
msgstr ""
#: howto/instrumentation.rst:40
msgid "On a Linux machine, this can be done via::"
msgstr ""
#: howto/instrumentation.rst:42
msgid "$ yum install systemtap-sdt-devel"
msgstr ""
#: howto/instrumentation.rst:44
msgid "or::"
msgstr ""
#: howto/instrumentation.rst:46
msgid "$ sudo apt-get install systemtap-sdt-dev"
msgstr ""
#: howto/instrumentation.rst:49
msgid ""
"CPython must then be :option:`configured with the --with-dtrace option <--"
"with-dtrace>`:"
msgstr ""
#: howto/instrumentation.rst:52
msgid "checking for --with-dtrace... yes"
msgstr ""
#: howto/instrumentation.rst:56
msgid ""
"On macOS, you can list available DTrace probes by running a Python process "
"in the background and listing all probes made available by the Python "
"provider::"
msgstr ""
#: howto/instrumentation.rst:60
msgid ""
"$ python3.6 -q &\n"
"$ sudo dtrace -l -P python$! # or: dtrace -l -m python3.6\n"
"\n"
" ID PROVIDER MODULE FUNCTION NAME\n"
"29564 python18035 python3.6 _PyEval_EvalFrameDefault "
"function-entry\n"
"29565 python18035 python3.6 dtrace_function_entry "
"function-entry\n"
"29566 python18035 python3.6 _PyEval_EvalFrameDefault "
"function-return\n"
"29567 python18035 python3.6 dtrace_function_return "
"function-return\n"
"29568 python18035 python3.6 collect gc-"
"done\n"
"29569 python18035 python3.6 collect gc-"
"start\n"
"29570 python18035 python3.6 _PyEval_EvalFrameDefault line\n"
"29571 python18035 python3.6 maybe_dtrace_line line"
msgstr ""
#: howto/instrumentation.rst:73
msgid ""
"On Linux, you can verify if the SystemTap static markers are present in the "
"built binary by seeing if it contains a \".note.stapsdt\" section."
msgstr ""
#: howto/instrumentation.rst:78
msgid ""
"$ readelf -S ./python | grep .note.stapsdt\n"
"[30] .note.stapsdt NOTE 0000000000000000 00308d78"
msgstr ""
#: howto/instrumentation.rst:81
msgid ""
"If you've built Python as a shared library (with the :option:`--enable-"
"shared` configure option), you need to look instead within the shared "
"library. For example::"
msgstr ""
#: howto/instrumentation.rst:85
msgid ""
"$ readelf -S libpython3.3dm.so.1.0 | grep .note.stapsdt\n"
"[29] .note.stapsdt NOTE 0000000000000000 00365b68"
msgstr ""
#: howto/instrumentation.rst:88
msgid "Sufficiently modern readelf can print the metadata::"
msgstr ""
#: howto/instrumentation.rst:90
msgid ""
"$ readelf -n ./python\n"
"\n"
"Displaying notes found at file offset 0x00000254 with length 0x00000020:\n"
" Owner Data size Description\n"
" GNU 0x00000010 NT_GNU_ABI_TAG (ABI version "
"tag)\n"
" OS: Linux, ABI: 2.6.32\n"
"\n"
"Displaying notes found at file offset 0x00000274 with length 0x00000024:\n"
" Owner Data size Description\n"
" GNU 0x00000014 NT_GNU_BUILD_ID (unique build "
"ID bitstring)\n"
" Build ID: df924a2b08a7e89f6e11251d4602022977af2670\n"
"\n"
"Displaying notes found at file offset 0x002d6c30 with length 0x00000144:\n"
" Owner Data size Description\n"
" stapsdt 0x00000031 NT_STAPSDT (SystemTap probe "
"descriptors)\n"
" Provider: python\n"
" Name: gc__start\n"
" Location: 0x00000000004371c3, Base: 0x0000000000630ce2, Semaphore: "
"0x00000000008d6bf6\n"
" Arguments: -4@%ebx\n"
" stapsdt 0x00000030 NT_STAPSDT (SystemTap probe "
"descriptors)\n"
" Provider: python\n"
" Name: gc__done\n"
" Location: 0x00000000004374e1, Base: 0x0000000000630ce2, Semaphore: "
"0x00000000008d6bf8\n"
" Arguments: -8@%rax\n"
" stapsdt 0x00000045 NT_STAPSDT (SystemTap probe "
"descriptors)\n"
" Provider: python\n"
" Name: function__entry\n"
" Location: 0x000000000053db6c, Base: 0x0000000000630ce2, Semaphore: "
"0x00000000008d6be8\n"
" Arguments: 8@%rbp 8@%r12 -4@%eax\n"
" stapsdt 0x00000046 NT_STAPSDT (SystemTap probe "
"descriptors)\n"
" Provider: python\n"
" Name: function__return\n"
" Location: 0x000000000053dba8, Base: 0x0000000000630ce2, Semaphore: "
"0x00000000008d6bea\n"
" Arguments: 8@%rbp 8@%r12 -4@%eax"
msgstr ""
#: howto/instrumentation.rst:125
msgid ""
"The above metadata contains information for SystemTap describing how it can "
"patch strategically placed machine code instructions to enable the tracing "
"hooks used by a SystemTap script."
msgstr ""
#: howto/instrumentation.rst:131
msgid "Static DTrace probes"
msgstr ""
#: howto/instrumentation.rst:133
msgid ""
"The following example DTrace script can be used to show the call/return "
"hierarchy of a Python script, only tracing within the invocation of a "
"function called \"start\". In other words, import-time function invocations "
"are not going to be listed:"
msgstr ""
#: howto/instrumentation.rst:138
msgid ""
"self int indent;\n"
"\n"
"python$target:::function-entry\n"
"/copyinstr(arg1) == \"start\"/\n"
"{\n"
" self->trace = 1;\n"
"}\n"
"\n"
"python$target:::function-entry\n"
"/self->trace/\n"
"{\n"
" printf(\"%d\\t%*s:\", timestamp, 15, probename);\n"
" printf(\"%*s\", self->indent, \"\");\n"
" printf(\"%s:%s:%d\\n\", basename(copyinstr(arg0)), copyinstr(arg1), "
"arg2);\n"
" self->indent++;\n"
"}\n"
"\n"
"python$target:::function-return\n"
"/self->trace/\n"
"{\n"
" self->indent--;\n"
" printf(\"%d\\t%*s:\", timestamp, 15, probename);\n"
" printf(\"%*s\", self->indent, \"\");\n"
" printf(\"%s:%s:%d\\n\", basename(copyinstr(arg0)), copyinstr(arg1), "
"arg2);\n"
"}\n"
"\n"
"python$target:::function-return\n"
"/copyinstr(arg1) == \"start\"/\n"
"{\n"
" self->trace = 0;\n"
"}"
msgstr ""
#: howto/instrumentation.rst:230
msgid "It can be invoked like this::"
msgstr ""
#: howto/instrumentation.rst:174
msgid "$ sudo dtrace -q -s call_stack.d -c \"python3.6 script.py\""
msgstr ""
#: howto/instrumentation.rst:236
msgid "The output looks like this:"
msgstr ""
#: howto/instrumentation.rst:178
msgid ""
"156641360502280 function-entry:call_stack.py:start:23\n"
"156641360518804 function-entry: call_stack.py:function_1:1\n"
"156641360532797 function-entry: call_stack.py:function_3:9\n"
"156641360546807 function-return: call_stack.py:function_3:10\n"
"156641360563367 function-return: call_stack.py:function_1:2\n"
"156641360578365 function-entry: call_stack.py:function_2:5\n"
"156641360591757 function-entry: call_stack.py:function_1:1\n"
"156641360605556 function-entry: call_stack.py:function_3:9\n"
"156641360617482 function-return: call_stack.py:function_3:10\n"
"156641360629814 function-return: call_stack.py:function_1:2\n"
"156641360642285 function-return: call_stack.py:function_2:6\n"
"156641360656770 function-entry: call_stack.py:function_3:9\n"
"156641360669707 function-return: call_stack.py:function_3:10\n"
"156641360687853 function-entry: call_stack.py:function_4:13\n"
"156641360700719 function-return: call_stack.py:function_4:14\n"
"156641360719640 function-entry: call_stack.py:function_5:18\n"
"156641360732567 function-return: call_stack.py:function_5:21\n"
"156641360747370 function-return:call_stack.py:start:28"
msgstr ""
#: howto/instrumentation.rst:201
msgid "Static SystemTap markers"
msgstr ""
#: howto/instrumentation.rst:203
msgid ""
"The low-level way to use the SystemTap integration is to use the static "
"markers directly. This requires you to explicitly state the binary file "
"containing them."
msgstr ""
#: howto/instrumentation.rst:207
msgid ""
"For example, this SystemTap script can be used to show the call/return "
"hierarchy of a Python script:"
msgstr ""
#: howto/instrumentation.rst:210
msgid ""
"probe process(\"python\").mark(\"function__entry\") {\n"
" filename = user_string($arg1);\n"
" funcname = user_string($arg2);\n"
" lineno = $arg3;\n"
"\n"
" printf(\"%s => %s in %s:%d\\\\n\",\n"
" thread_indent(1), funcname, filename, lineno);\n"
"}\n"
"\n"
"probe process(\"python\").mark(\"function__return\") {\n"
" filename = user_string($arg1);\n"
" funcname = user_string($arg2);\n"
" lineno = $arg3;\n"
"\n"
" printf(\"%s <= %s in %s:%d\\\\n\",\n"
" thread_indent(-1), funcname, filename, lineno);\n"
"}"
msgstr ""
#: howto/instrumentation.rst:232
msgid ""
"$ stap \\\n"
" show-call-hierarchy.stp \\\n"
" -c \"./python test.py\""
msgstr ""
#: howto/instrumentation.rst:238
msgid ""
"11408 python(8274): => __contains__ in Lib/_abcoll.py:362\n"
"11414 python(8274): => __getitem__ in Lib/os.py:425\n"
"11418 python(8274): => encode in Lib/os.py:490\n"
"11424 python(8274): <= encode in Lib/os.py:493\n"
"11428 python(8274): <= __getitem__ in Lib/os.py:426\n"
"11433 python(8274): <= __contains__ in Lib/_abcoll.py:366"
msgstr ""
#: howto/instrumentation.rst:247
msgid "where the columns are:"
msgstr ""
#: howto/instrumentation.rst:249
msgid "time in microseconds since start of script"
msgstr ""
#: howto/instrumentation.rst:250
msgid "name of executable"
msgstr ""
#: howto/instrumentation.rst:251
msgid "PID of process"
msgstr ""
#: howto/instrumentation.rst:253
msgid ""
"and the remainder indicates the call/return hierarchy as the script executes."
msgstr ""
#: howto/instrumentation.rst:255
msgid ""
"For a :option:`--enable-shared` build of CPython, the markers are contained "
"within the libpython shared library, and the probe's dotted path needs to "
"reflect this. For example, this line from the above example:"
msgstr ""
#: howto/instrumentation.rst:259
msgid "probe process(\"python\").mark(\"function__entry\") {"
msgstr ""
#: howto/instrumentation.rst:263
msgid "should instead read:"
msgstr ""
#: howto/instrumentation.rst:265
msgid ""
"probe process(\"python\").library(\"libpython3.6dm.so.1.0\")."
"mark(\"function__entry\") {"
msgstr ""
#: howto/instrumentation.rst:269
msgid "(assuming a :ref:`debug build <debug-build>` of CPython 3.6)"
msgstr ""
#: howto/instrumentation.rst:273
msgid "Available static markers"
msgstr ""
#: howto/instrumentation.rst:277
msgid ""
"This marker indicates that execution of a Python function has begun. It is "
"only triggered for pure-Python (bytecode) functions."
msgstr ""
#: howto/instrumentation.rst:280
msgid ""
"The filename, function name, and line number are provided back to the "
"tracing script as positional arguments, which must be accessed using "
"``$arg1``, ``$arg2``, ``$arg3``:"
msgstr ""
#: howto/instrumentation.rst:284
msgid ""
"``$arg1`` : ``(const char *)`` filename, accessible using "
"``user_string($arg1)``"
msgstr ""
#: howto/instrumentation.rst:286
msgid ""
"``$arg2`` : ``(const char *)`` function name, accessible using "
"``user_string($arg2)``"
msgstr ""
#: howto/instrumentation.rst:289
msgid "``$arg3`` : ``int`` line number"
msgstr ""
#: howto/instrumentation.rst:293
msgid ""
"This marker is the converse of :c:func:`!function__entry`, and indicates "
"that execution of a Python function has ended (either via ``return``, or via "
"an exception). It is only triggered for pure-Python (bytecode) functions."
msgstr ""
#: howto/instrumentation.rst:297
msgid "The arguments are the same as for :c:func:`!function__entry`"
msgstr ""
#: howto/instrumentation.rst:301
msgid ""
"This marker indicates a Python line is about to be executed. It is the "
"equivalent of line-by-line tracing with a Python profiler. It is not "
"triggered within C functions."
msgstr ""
#: howto/instrumentation.rst:305
msgid "The arguments are the same as for :c:func:`!function__entry`."
msgstr ""
#: howto/instrumentation.rst:309
msgid ""
"Fires when the Python interpreter starts a garbage collection cycle. "
"``arg0`` is the generation to scan, like :func:`gc.collect`."
msgstr ""
#: howto/instrumentation.rst:314
msgid ""
"Fires when the Python interpreter finishes a garbage collection cycle. "
"``arg0`` is the number of collected objects."
msgstr ""
#: howto/instrumentation.rst:319
msgid ""
"Fires before :mod:`importlib` attempts to find and load the module. ``arg0`` "
"is the module name."
msgstr ""
#: howto/instrumentation.rst:326
msgid ""
"Fires after :mod:`importlib`'s find_and_load function is called. ``arg0`` is "
"the module name, ``arg1`` indicates if module was successfully loaded."
msgstr ""
#: howto/instrumentation.rst:335
msgid ""
"Fires when :func:`sys.audit` or :c:func:`PySys_Audit` is called. ``arg0`` is "
"the event name as C string, ``arg1`` is a :c:type:`PyObject` pointer to a "
"tuple object."
msgstr ""
#: howto/instrumentation.rst:343
msgid "SystemTap Tapsets"
msgstr ""
#: howto/instrumentation.rst:345
msgid ""
"The higher-level way to use the SystemTap integration is to use a "
"\"tapset\": SystemTap's equivalent of a library, which hides some of the "
"lower-level details of the static markers."
msgstr ""
#: howto/instrumentation.rst:349
msgid "Here is a tapset file, based on a non-shared build of CPython:"
msgstr ""
#: howto/instrumentation.rst:351
msgid ""
"/*\n"
" Provide a higher-level wrapping around the function__entry and\n"
" function__return markers:\n"
" \\*/\n"
"probe python.function.entry = process(\"python\").mark(\"function__entry\")\n"
"{\n"
" filename = user_string($arg1);\n"
" funcname = user_string($arg2);\n"
" lineno = $arg3;\n"
" frameptr = $arg4\n"
"}\n"
"probe python.function.return = process(\"python\")."
"mark(\"function__return\")\n"
"{\n"
" filename = user_string($arg1);\n"
" funcname = user_string($arg2);\n"
" lineno = $arg3;\n"
" frameptr = $arg4\n"
"}"
msgstr ""
#: howto/instrumentation.rst:372
msgid ""
"If this file is installed in SystemTap's tapset directory (e.g. ``/usr/share/"
"systemtap/tapset``), then these additional probepoints become available:"
msgstr ""
#: howto/instrumentation.rst:378
msgid ""
"This probe point indicates that execution of a Python function has begun. It "
"is only triggered for pure-Python (bytecode) functions."
msgstr ""
#: howto/instrumentation.rst:383
msgid ""
"This probe point is the converse of ``python.function.return``, and "
"indicates that execution of a Python function has ended (either via "
"``return``, or via an exception). It is only triggered for pure-Python "
"(bytecode) functions."
msgstr ""
#: howto/instrumentation.rst:390
msgid "Examples"
msgstr ""
#: howto/instrumentation.rst:391
msgid ""
"This SystemTap script uses the tapset above to more cleanly implement the "
"example given above of tracing the Python function-call hierarchy, without "
"needing to directly name the static markers:"
msgstr ""
#: howto/instrumentation.rst:395
msgid ""
"probe python.function.entry\n"
"{\n"
" printf(\"%s => %s in %s:%d\\n\",\n"
" thread_indent(1), funcname, filename, lineno);\n"
"}\n"
"\n"
"probe python.function.return\n"
"{\n"
" printf(\"%s <= %s in %s:%d\\n\",\n"
" thread_indent(-1), funcname, filename, lineno);\n"
"}"
msgstr ""
#: howto/instrumentation.rst:410
msgid ""
"The following script uses the tapset above to provide a top-like view of all "
"running CPython code, showing the top 20 most frequently entered bytecode "
"frames, each second, across the whole system:"
msgstr ""
#: howto/instrumentation.rst:414
msgid ""
"global fn_calls;\n"
"\n"
"probe python.function.entry\n"
"{\n"
" fn_calls[pid(), filename, funcname, lineno] += 1;\n"
"}\n"
"\n"
"probe timer.ms(1000) {\n"
" printf(\"\\033[2J\\033[1;1H\") /* clear screen \\*/\n"
" printf(\"%6s %80s %6s %30s %6s\\n\",\n"
" \"PID\", \"FILENAME\", \"LINE\", \"FUNCTION\", \"CALLS\")\n"
" foreach ([pid, filename, funcname, lineno] in fn_calls- limit 20) {\n"
" printf(\"%6d %80s %6d %30s %6d\\n\",\n"
" pid, filename, lineno, funcname,\n"
" fn_calls[pid, filename, funcname, lineno]);\n"
" }\n"
" delete fn_calls;\n"
"}"
msgstr ""