Repository navigation
Expand file tree
/
Copy pathremote_debugging.po
More file actions
889 lines (750 loc) · 30.3 KB
/
Copy pathremote_debugging.po
File metadata and controls
889 lines (750 loc) · 30.3 KB
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
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
# Copyright (C) 2001 Python Software Foundation
# This file is distributed under the same license as the Python package.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Python 3\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2026-10-17 14:27+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: FRENCH <traductions@lists.afpy.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: howto/remote_debugging.rst:4
msgid "Remote debugging attachment protocol"
msgstr ""
#: howto/remote_debugging.rst:6
msgid ""
"This protocol enables external tools to attach to a running CPython process "
"and execute Python code remotely."
msgstr ""
#: howto/remote_debugging.rst:9
msgid ""
"Most platforms require elevated privileges to attach to another Python "
"process."
msgstr ""
#: howto/remote_debugging.rst:12
msgid "Disabling remote debugging"
msgstr ""
#: howto/remote_debugging.rst:14
msgid "To disable remote debugging support, use any of the following:"
msgstr ""
#: howto/remote_debugging.rst:16
msgid ""
"Set the :envvar:`PYTHON_DISABLE_REMOTE_DEBUG` environment variable to ``1`` "
"before starting the interpreter."
msgstr ""
#: howto/remote_debugging.rst:18
msgid "Use the :option:`-X disable_remote_debug` command-line option."
msgstr ""
#: howto/remote_debugging.rst:19
msgid "Compile Python with the :option:`--without-remote-debug` build flag."
msgstr ""
#: howto/remote_debugging.rst:24
msgid "Permission requirements"
msgstr ""
#: howto/remote_debugging.rst:26
msgid ""
"Attaching to a running Python process for remote debugging requires elevated "
"privileges on most platforms. The specific requirements and troubleshooting "
"steps depend on your operating system:"
msgstr ""
#: howto/remote_debugging.rst:31
msgid "Linux"
msgstr "Linux"
#: howto/remote_debugging.rst:32
msgid ""
"The tracer process must have the ``CAP_SYS_PTRACE`` capability or equivalent "
"privileges. You can only trace processes you own and can signal. Tracing may "
"fail if the process is already being traced, or if it is running with set-"
"user-ID or set-group-ID. Security modules like Yama may further restrict "
"tracing."
msgstr ""
#: howto/remote_debugging.rst:38
msgid "To temporarily relax ptrace restrictions (until reboot), run:"
msgstr ""
#: howto/remote_debugging.rst:40
msgid "``echo 0 | sudo tee /proc/sys/kernel/yama/ptrace_scope``"
msgstr ""
#: howto/remote_debugging.rst:44
msgid ""
"Disabling ``ptrace_scope`` reduces system hardening and should only be done "
"in trusted environments."
msgstr ""
#: howto/remote_debugging.rst:47
msgid ""
"If running inside a container, use ``--cap-add=SYS_PTRACE`` or ``--"
"privileged``, and run as root if needed."
msgstr ""
#: howto/remote_debugging.rst:50
msgid "Try re-running the command with elevated privileges:"
msgstr ""
#: howto/remote_debugging.rst:52
msgid "``sudo -E !!``"
msgstr ""
#: howto/remote_debugging.rst:56
msgid "macOS"
msgstr "macOS"
#: howto/remote_debugging.rst:57
msgid ""
"To attach to another process, you typically need to run your debugging tool "
"with elevated privileges. This can be done by using ``sudo`` or running as "
"root."
msgstr ""
#: howto/remote_debugging.rst:61
msgid ""
"Even when attaching to processes you own, macOS may block debugging unless "
"the debugger is run with root privileges due to system security restrictions."
msgstr ""
#: howto/remote_debugging.rst:66
msgid "Windows"
msgstr "Windows"
#: howto/remote_debugging.rst:67
msgid ""
"To attach to another process, you usually need to run your debugging tool "
"with administrative privileges. Start the command prompt or terminal as "
"Administrator."
msgstr ""
#: howto/remote_debugging.rst:71
msgid ""
"Some processes may still be inaccessible even with Administrator rights, "
"unless you have the ``SeDebugPrivilege`` privilege enabled."
msgstr ""
#: howto/remote_debugging.rst:74
msgid ""
"To resolve file or folder access issues, adjust the security permissions:"
msgstr ""
#: howto/remote_debugging.rst:76
msgid "Right-click the file or folder and select **Properties**."
msgstr ""
#: howto/remote_debugging.rst:77
msgid "Go to the **Security** tab to view users and groups with access."
msgstr ""
#: howto/remote_debugging.rst:78
msgid "Click **Edit** to modify permissions."
msgstr ""
#: howto/remote_debugging.rst:79
msgid "Select your user account."
msgstr ""
#: howto/remote_debugging.rst:80
msgid "In **Permissions**, check **Read** or **Full control** as needed."
msgstr ""
#: howto/remote_debugging.rst:81
msgid "Click **Apply**, then **OK** to confirm."
msgstr ""
#: howto/remote_debugging.rst:86
msgid ""
"Ensure you've satisfied all :ref:`permission-requirements` before proceeding."
msgstr ""
#: howto/remote_debugging.rst:88
msgid ""
"This section describes the low-level protocol that enables external tools to "
"inject and execute a Python script within a running CPython process."
msgstr ""
#: howto/remote_debugging.rst:91
msgid ""
"This mechanism forms the basis of the :func:`sys.remote_exec` function, "
"which instructs a remote Python process to execute a ``.py`` file. However, "
"this section does not document the usage of that function. Instead, it "
"provides a detailed explanation of the underlying protocol, which takes as "
"input the ``pid`` of a target Python process and the path to a Python source "
"file to be executed. This information supports independent reimplementation "
"of the protocol, regardless of programming language."
msgstr ""
#: howto/remote_debugging.rst:101
msgid ""
"The execution of the injected script depends on the interpreter reaching a "
"safe evaluation point. As a result, execution may be delayed depending on "
"the runtime state of the target process."
msgstr ""
#: howto/remote_debugging.rst:105
msgid ""
"Once injected, the script is executed by the interpreter within the target "
"process the next time a safe evaluation point is reached. This approach "
"enables remote execution capabilities without modifying the behavior or "
"structure of the running Python application."
msgstr ""
#: howto/remote_debugging.rst:110
msgid ""
"Subsequent sections provide a step-by-step description of the protocol, "
"including techniques for locating interpreter structures in memory, safely "
"accessing internal fields, and triggering code execution. Platform-specific "
"variations are noted where applicable, and example implementations are "
"included to clarify each operation."
msgstr ""
#: howto/remote_debugging.rst:117
msgid "Locating the PyRuntime structure"
msgstr ""
#: howto/remote_debugging.rst:119
msgid ""
"CPython places the ``PyRuntime`` structure in a dedicated binary section to "
"help external tools find it at runtime. The name and format of this section "
"vary by platform. For example, ``.PyRuntime`` is used on ELF systems, and "
"``__DATA,__PyRuntime`` is used on macOS. Tools can find the offset of this "
"structure by examining the binary on disk."
msgstr ""
#: howto/remote_debugging.rst:125
msgid ""
"The ``PyRuntime`` structure contains CPython’s global interpreter state and "
"provides access to other internal data, including the list of interpreters, "
"thread states, and debugger support fields."
msgstr ""
#: howto/remote_debugging.rst:129
msgid ""
"To work with a remote Python process, a debugger must first find the memory "
"address of the ``PyRuntime`` structure in the target process. This address "
"can’t be hardcoded or calculated from a symbol name, because it depends on "
"where the operating system loaded the binary."
msgstr ""
#: howto/remote_debugging.rst:134
msgid ""
"The method for finding ``PyRuntime`` depends on the platform, but the steps "
"are the same in general:"
msgstr ""
#: howto/remote_debugging.rst:137
msgid ""
"Find the base address where the Python binary or shared library was loaded "
"in the target process."
msgstr ""
#: howto/remote_debugging.rst:139
msgid ""
"Use the on-disk binary to locate the offset of the ``.PyRuntime`` section."
msgstr ""
#: howto/remote_debugging.rst:140
msgid ""
"Add the section offset to the base address to compute the address in memory."
msgstr ""
#: howto/remote_debugging.rst:142
msgid ""
"The sections below explain how to do this on each supported platform and "
"include example code."
msgstr ""
#: howto/remote_debugging.rst:146
msgid "Linux (ELF)"
msgstr ""
#: howto/remote_debugging.rst:147
msgid "To find the ``PyRuntime`` structure on Linux:"
msgstr ""
#: howto/remote_debugging.rst:149
msgid ""
"Read the process’s memory map (for example, ``/proc/<pid>/maps``) to find "
"the address where the Python executable or ``libpython`` was loaded."
msgstr ""
#: howto/remote_debugging.rst:151
msgid ""
"Parse the ELF section headers in the binary to get the offset of the "
"``.PyRuntime`` section."
msgstr ""
#: howto/remote_debugging.rst:153
msgid ""
"Add that offset to the base address from step 1 to get the memory address of "
"``PyRuntime``."
msgstr ""
#: howto/remote_debugging.rst:218 howto/remote_debugging.rst:557
msgid "The following is an example implementation::"
msgstr ""
#: howto/remote_debugging.rst:179
msgid ""
"On Linux systems, there are two main approaches to read memory from another "
"process. The first is through the ``/proc`` filesystem, specifically by "
"reading from ``/proc/[pid]/mem`` which provides direct access to the "
"process's memory. This requires appropriate permissions - either being the "
"same user as the target process or having root access. The second approach "
"is using the ``process_vm_readv()`` system call which provides a more "
"efficient way to copy memory between processes. While ptrace's "
"``PTRACE_PEEKTEXT`` operation can also be used to read memory, it is "
"significantly slower as it only reads one word at a time and requires "
"multiple context switches between the tracer and tracee processes."
msgstr ""
#: howto/remote_debugging.rst:190
msgid ""
"For parsing ELF sections, the process involves reading and interpreting the "
"ELF file format structures from the binary file on disk. The ELF header "
"contains a pointer to the section header table. Each section header contains "
"metadata about a section including its name (stored in a separate string "
"table), offset, and size. To find a specific section like .PyRuntime, you "
"need to walk through these headers and match the section name. The section "
"header then provides the offset where that section exists in the file, which "
"can be used to calculate its runtime address when the binary is loaded into "
"memory."
msgstr ""
#: howto/remote_debugging.rst:199
msgid ""
"You can read more about the ELF file format in the `ELF specification "
"<https://en.wikipedia.org/wiki/Executable_and_Linkable_Format>`_."
msgstr ""
#: howto/remote_debugging.rst:204
msgid "macOS (Mach-O)"
msgstr ""
#: howto/remote_debugging.rst:205
msgid "To find the ``PyRuntime`` structure on macOS:"
msgstr ""
#: howto/remote_debugging.rst:207
msgid ""
"Call ``task_for_pid()`` to get the ``mach_port_t`` task port for the target "
"process. This handle is needed to read memory using APIs like "
"``mach_vm_read_overwrite`` and ``mach_vm_region``."
msgstr ""
#: howto/remote_debugging.rst:210
msgid ""
"Scan the memory regions to find the one containing the Python executable or "
"``libpython``."
msgstr ""
#: howto/remote_debugging.rst:212
msgid ""
"Load the binary file from disk and parse the Mach-O headers to find the "
"section named ``PyRuntime`` in the ``__DATA`` segment. On macOS, symbol "
"names are automatically prefixed with an underscore, so the ``PyRuntime`` "
"symbol appears as ``_PyRuntime`` in the symbol table, but the section name "
"is not affected."
msgstr ""
#: howto/remote_debugging.rst:243
msgid ""
"On macOS, accessing another process's memory requires using Mach-O specific "
"APIs and file formats. The first step is obtaining a ``task_port`` handle "
"via ``task_for_pid()``, which provides access to the target process's memory "
"space. This handle enables memory operations through APIs like "
"``mach_vm_read_overwrite()``."
msgstr ""
#: howto/remote_debugging.rst:249
msgid ""
"The process memory can be examined using ``mach_vm_region()`` to scan "
"through the virtual memory space, while ``proc_regionfilename()`` helps "
"identify which binary files are loaded at each memory region. When the "
"Python binary or library is found, its Mach-O headers need to be parsed to "
"locate the ``PyRuntime`` structure."
msgstr ""
#: howto/remote_debugging.rst:254
msgid ""
"The Mach-O format organizes code and data into segments and sections. The "
"``PyRuntime`` structure lives in a section named ``__PyRuntime`` within the "
"``__DATA`` segment. The actual runtime address calculation involves finding "
"the ``__TEXT`` segment which serves as the binary's base address, then "
"locating the ``__DATA`` segment containing our target section. The final "
"address is computed by combining the base address with the appropriate "
"section offsets from the Mach-O headers."
msgstr ""
#: howto/remote_debugging.rst:262
msgid ""
"Note that accessing another process's memory on macOS typically requires "
"elevated privileges - either root access or special security entitlements "
"granted to the debugging process."
msgstr ""
#: howto/remote_debugging.rst:268
msgid "Windows (PE)"
msgstr ""
#: howto/remote_debugging.rst:269
msgid "To find the ``PyRuntime`` structure on Windows:"
msgstr ""
#: howto/remote_debugging.rst:271
msgid ""
"Use the ToolHelp API to enumerate all modules loaded in the target process. "
"This is done using functions such as `CreateToolhelp32Snapshot <https://"
"learn.microsoft.com/en-us/windows/win32/api/tlhelp32/nf-tlhelp32-"
"createtoolhelp32snapshot>`_, `Module32First <https://learn.microsoft.com/en-"
"us/windows/win32/api/tlhelp32/nf-tlhelp32-module32first>`_, and "
"`Module32Next <https://learn.microsoft.com/en-us/windows/win32/api/tlhelp32/"
"nf-tlhelp32-module32next>`_."
msgstr ""
#: howto/remote_debugging.rst:278
msgid ""
"Identify the module corresponding to :file:`python.exe` "
"or :file:`python{XY}.dll`, where ``X`` and ``Y`` are the major and minor "
"version numbers of the Python version, and record its base address."
msgstr ""
#: howto/remote_debugging.rst:281
msgid ""
"Locate the ``PyRuntim`` section. Due to the PE format's 8-character limit on "
"section names (defined as ``IMAGE_SIZEOF_SHORT_NAME``), the original name "
"``PyRuntime`` is truncated. This section contains the ``PyRuntime`` "
"structure."
msgstr ""
#: howto/remote_debugging.rst:285
msgid ""
"Retrieve the section’s relative virtual address (RVA) and add it to the base "
"address of the module."
msgstr ""
#: howto/remote_debugging.rst:312
msgid ""
"On Windows, accessing another process's memory requires using the Windows "
"API functions like ``CreateToolhelp32Snapshot()`` and ``Module32First()/"
"Module32Next()`` to enumerate loaded modules. The ``OpenProcess()`` function "
"provides a handle to access the target process's memory space, enabling "
"memory operations through ``ReadProcessMemory()``."
msgstr ""
#: howto/remote_debugging.rst:318
msgid ""
"The process memory can be examined by enumerating loaded modules to find the "
"Python binary or DLL. When found, its PE headers need to be parsed to locate "
"the ``PyRuntime`` structure."
msgstr ""
#: howto/remote_debugging.rst:322
msgid ""
"The PE format organizes code and data into sections. The ``PyRuntime`` "
"structure lives in a section named \"PyRuntim\" (truncated from "
"\"PyRuntime\" due to PE's 8-character name limit). The actual runtime "
"address calculation involves finding the module's base address from the "
"module entry, then locating our target section in the PE headers. The final "
"address is computed by combining the base address with the section's virtual "
"address from the PE section headers."
msgstr ""
#: howto/remote_debugging.rst:329
msgid ""
"Note that accessing another process's memory on Windows typically requires "
"appropriate privileges - either administrative access or the "
"``SeDebugPrivilege`` privilege granted to the debugging process."
msgstr ""
#: howto/remote_debugging.rst:335
msgid "Reading _Py_DebugOffsets"
msgstr ""
#: howto/remote_debugging.rst:337
msgid ""
"Once the address of the ``PyRuntime`` structure has been determined, the "
"next step is to read the ``_Py_DebugOffsets`` structure located at the "
"beginning of the ``PyRuntime`` block."
msgstr ""
#: howto/remote_debugging.rst:341
msgid ""
"This structure provides version-specific field offsets that are needed to "
"safely read interpreter and thread state memory. These offsets vary between "
"CPython versions and must be checked before use to ensure they are "
"compatible."
msgstr ""
#: howto/remote_debugging.rst:345
msgid "To read and check the debug offsets, follow these steps:"
msgstr ""
#: howto/remote_debugging.rst:347
msgid ""
"Read memory from the target process starting at the ``PyRuntime`` address, "
"covering the same number of bytes as the ``_Py_DebugOffsets`` structure. "
"This structure is located at the very start of the ``PyRuntime`` memory "
"block. Its layout is defined in CPython’s internal headers and stays the "
"same within a given minor version, but may change in major versions."
msgstr ""
#: howto/remote_debugging.rst:353
msgid "Check that the structure contains valid data:"
msgstr ""
#: howto/remote_debugging.rst:355
msgid "The ``cookie`` field must match the expected debug marker."
msgstr ""
#: howto/remote_debugging.rst:356
msgid ""
"The ``version`` field must match the version of the Python interpreter used "
"by the debugger."
msgstr ""
#: howto/remote_debugging.rst:358
msgid ""
"If either the debugger or the target process is using a pre-release version "
"(for example, an alpha, beta, or release candidate), the versions must match "
"exactly."
msgstr ""
#: howto/remote_debugging.rst:361
msgid ""
"The ``free_threaded`` field must have the same value in both the debugger "
"and the target process."
msgstr ""
#: howto/remote_debugging.rst:364
msgid ""
"If the structure is valid, the offsets it contains can be used to locate "
"fields in memory. If any check fails, the debugger should stop the operation "
"to avoid reading memory in the wrong format."
msgstr ""
#: howto/remote_debugging.rst:368
msgid ""
"The following is an example implementation that reads and checks "
"``_Py_DebugOffsets``::"
msgstr ""
#: howto/remote_debugging.rst:396
msgid "**Process suspension recommended**"
msgstr ""
#: howto/remote_debugging.rst:398
msgid ""
"To avoid race conditions and ensure memory consistency, it is strongly "
"recommended that the target process be suspended before performing any "
"operations that read or write internal interpreter state. The Python runtime "
"may concurrently mutate interpreter data structures—such as creating or "
"destroying threads—during normal execution. This can result in invalid "
"memory reads or writes."
msgstr ""
#: howto/remote_debugging.rst:405
msgid ""
"A debugger may suspend execution by attaching to the process with ``ptrace`` "
"or by sending a ``SIGSTOP`` signal. Execution should only be resumed after "
"debugger-side memory operations are complete."
msgstr ""
#: howto/remote_debugging.rst:411
msgid ""
"Some tools, such as profilers or sampling-based debuggers, may operate on a "
"running process without suspension. In such cases, tools must be explicitly "
"designed to handle partially updated or inconsistent memory. For most "
"debugger implementations, suspending the process remains the safest and most "
"robust approach."
msgstr ""
#: howto/remote_debugging.rst:419
msgid "Locating the interpreter and thread state"
msgstr ""
#: howto/remote_debugging.rst:421
msgid ""
"Before code can be injected and executed in a remote Python process, the "
"debugger must choose a thread in which to schedule execution. This is "
"necessary because the control fields used to perform remote code injection "
"are located in the ``_PyRemoteDebuggerSupport`` structure, which is embedded "
"in a ``PyThreadState`` object. These fields are modified by the debugger to "
"request execution of injected scripts."
msgstr ""
#: howto/remote_debugging.rst:428
msgid ""
"The ``PyThreadState`` structure represents a thread running inside a Python "
"interpreter. It maintains the thread’s evaluation context and contains the "
"fields required for debugger coordination. Locating a valid "
"``PyThreadState`` is therefore a key prerequisite for triggering execution "
"remotely."
msgstr ""
#: howto/remote_debugging.rst:433
msgid ""
"A thread is typically selected based on its role or ID. In most cases, the "
"main thread is used, but some tools may target a specific thread by its "
"native thread ID. Once the target thread is chosen, the debugger must locate "
"both the interpreter and the associated thread state structures in memory."
msgstr ""
#: howto/remote_debugging.rst:438
msgid "The relevant internal structures are defined as follows:"
msgstr ""
#: howto/remote_debugging.rst:440
msgid ""
"``PyInterpreterState`` represents an isolated Python interpreter instance. "
"Each interpreter maintains its own set of imported modules, built-in state, "
"and thread state list. Although most Python applications use a single "
"interpreter, CPython supports multiple interpreters in the same process."
msgstr ""
#: howto/remote_debugging.rst:445
msgid ""
"``PyThreadState`` represents a thread running within an interpreter. It "
"contains execution state and the control fields used by the debugger."
msgstr ""
#: howto/remote_debugging.rst:448
msgid "To locate a thread:"
msgstr ""
#: howto/remote_debugging.rst:450
msgid ""
"Use the offset ``runtime_state.interpreters_head`` to obtain the address of "
"the first interpreter in the ``PyRuntime`` structure. This is the entry "
"point to the linked list of active interpreters."
msgstr ""
#: howto/remote_debugging.rst:454
msgid ""
"Use the offset ``interpreter_state.threads_main`` to access the main thread "
"state associated with the selected interpreter. This is typically the most "
"reliable thread to target."
msgstr ""
#: howto/remote_debugging.rst:458
msgid ""
"Optionally, use the offset ``interpreter_state.threads_head`` to iterate "
"through the linked list of all thread states. Each ``PyThreadState`` "
"structure contains a ``native_thread_id`` field, which may be compared to a "
"target thread ID to find a specific thread."
msgstr ""
#: howto/remote_debugging.rst:463
msgid ""
"Once a valid ``PyThreadState`` has been found, its address can be used in "
"later steps of the protocol, such as writing debugger control fields and "
"scheduling execution."
msgstr ""
#: howto/remote_debugging.rst:467
msgid ""
"The following is an example implementation that locates the main thread "
"state::"
msgstr ""
#: howto/remote_debugging.rst:490
msgid ""
"The following example demonstrates how to locate a thread by its native "
"thread ID::"
msgstr ""
#: howto/remote_debugging.rst:520
msgid ""
"Once a valid thread state has been located, the debugger can proceed with "
"modifying its control fields and scheduling execution, as described in the "
"next section."
msgstr ""
#: howto/remote_debugging.rst:525
msgid "Writing control information"
msgstr ""
#: howto/remote_debugging.rst:527
msgid ""
"Once a valid ``PyThreadState`` structure has been identified, the debugger "
"may modify control fields within it to schedule the execution of a specified "
"Python script. These control fields are checked periodically by the "
"interpreter, and when set correctly, they trigger the execution of remote "
"code at a safe point in the evaluation loop."
msgstr ""
#: howto/remote_debugging.rst:533
msgid ""
"Each ``PyThreadState`` contains a ``_PyRemoteDebuggerSupport`` structure "
"used for communication between the debugger and the interpreter. The "
"locations of its fields are defined by the ``_Py_DebugOffsets`` structure "
"and include the following:"
msgstr ""
#: howto/remote_debugging.rst:538
msgid ""
"``debugger_script_path``: A fixed-size buffer that holds the full path to a "
"Python source file (``.py``). This file must be accessible and readable by "
"the target process when execution is triggered."
msgstr ""
#: howto/remote_debugging.rst:542
msgid ""
"``debugger_pending_call``: An integer flag. Setting this to ``1`` tells the "
"interpreter that a script is ready to be executed."
msgstr ""
#: howto/remote_debugging.rst:545
msgid ""
"``eval_breaker``: A field checked by the interpreter during execution. "
"Setting bit 5 (``_PY_EVAL_PLEASE_STOP_BIT``, value ``1U << 5``) in this "
"field causes the interpreter to pause and check for debugger activity."
msgstr ""
#: howto/remote_debugging.rst:549
msgid ""
"To complete the injection, the debugger must perform the following steps:"
msgstr ""
#: howto/remote_debugging.rst:551
msgid "Write the full script path into the ``debugger_script_path`` buffer."
msgstr ""
#: howto/remote_debugging.rst:552
msgid "Set ``debugger_pending_call`` to ``1``."
msgstr ""
#: howto/remote_debugging.rst:553
msgid ""
"Read the current value of ``eval_breaker``, set bit 5 "
"(``_PY_EVAL_PLEASE_STOP_BIT``), and write the updated value back. This "
"signals the interpreter to check for debugger activity."
msgstr ""
#: howto/remote_debugging.rst:596
msgid ""
"Once these fields are set, the debugger may resume the process (if it was "
"suspended). The interpreter will process the request at the next safe "
"evaluation point, load the script from disk, and execute it."
msgstr ""
#: howto/remote_debugging.rst:600
msgid ""
"It is the responsibility of the debugger to ensure that the script file "
"remains present and accessible to the target process during execution."
msgstr ""
#: howto/remote_debugging.rst:605
msgid ""
"Script execution is asynchronous. The script file cannot be deleted "
"immediately after injection. The debugger should wait until the injected "
"script has produced an observable effect before removing the file. This "
"effect depends on what the script is designed to do. For example, a debugger "
"might wait until the remote process connects back to a socket before "
"removing the script. Once such an effect is observed, it is safe to assume "
"the file is no longer needed."
msgstr ""
#: howto/remote_debugging.rst:614
msgid "Summary"
msgstr ""
#: howto/remote_debugging.rst:616
msgid "To inject and execute a Python script in a remote process:"
msgstr ""
#: howto/remote_debugging.rst:618
msgid "Locate the ``PyRuntime`` structure in the target process’s memory."
msgstr ""
#: howto/remote_debugging.rst:619
msgid ""
"Read and validate the ``_Py_DebugOffsets`` structure at the beginning of "
"``PyRuntime``."
msgstr ""
#: howto/remote_debugging.rst:621
msgid "Use the offsets to locate a valid ``PyThreadState``."
msgstr ""
#: howto/remote_debugging.rst:622
msgid "Write the path to a Python script into ``debugger_script_path``."
msgstr ""
#: howto/remote_debugging.rst:623
msgid "Set the ``debugger_pending_call`` flag to ``1``."
msgstr ""
#: howto/remote_debugging.rst:624
msgid "Set ``_PY_EVAL_PLEASE_STOP_BIT`` in the ``eval_breaker`` field."
msgstr ""
#: howto/remote_debugging.rst:625
msgid ""
"Resume the process (if suspended). The script will execute at the next safe "
"evaluation point."
msgstr ""
#: howto/remote_debugging.rst:631
msgid "Security and threat model"
msgstr ""
#: howto/remote_debugging.rst:633
msgid ""
"The remote debugging protocol relies on the same operating system primitives "
"used by native debuggers such as GDB and LLDB. Attaching to a process "
"requires the **same privileges** that those debuggers require, for example "
"``ptrace`` / Yama LSM on Linux, ``task_for_pid`` on macOS, and "
"``SeDebugPrivilege`` on Windows. Python does not introduce any new "
"privilege escalation path; if an attacker already possesses the permissions "
"needed to attach to a process, they could equally use GDB to read memory or "
"inject code."
msgstr ""
#: howto/remote_debugging.rst:642
msgid ""
"The following principles define what is, and is not, considered a security "
"vulnerability in this feature:"
msgstr ""
#: howto/remote_debugging.rst:645
msgid "Attaching requires OS-level privileges"
msgstr ""
#: howto/remote_debugging.rst:646
msgid ""
"On every supported platform the operating system gates cross-process memory "
"access behind privilege checks (``CAP_SYS_PTRACE``, root, or administrator "
"rights). A report that demonstrates an issue only after these privileges "
"have already been obtained is **not** a vulnerability in CPython, since the "
"OS security boundary was already crossed."
msgstr ""
#: howto/remote_debugging.rst:652
msgid ""
"Crashes or memory errors when reading a compromised process are not "
"vulnerabilities"
msgstr ""
#: howto/remote_debugging.rst:653
msgid ""
"A tool that reads internal interpreter state from a target process must "
"trust that memory to be well-formed. If the target process has been "
"corrupted or is controlled by an attacker, the debugger or profiler may "
"crash, produce garbage output, or behave unpredictably. This is the same "
"risk accepted by every ``ptrace``-based debugger. Bugs in this category "
"(buffer overflows, segmentation faults, or undefined behaviour triggered by "
"reading corrupted state) are **not** treated as security issues, though "
"fixes that improve robustness are welcome."
msgstr ""
#: howto/remote_debugging.rst:662
msgid "Vulnerabilities in the target process are not in scope"
msgstr ""
#: howto/remote_debugging.rst:663
msgid ""
"If the Python process being debugged has already been compromised, the "
"attacker already controls execution in that process. Demonstrating further "
"impact from that starting point does not constitute a vulnerability in the "
"remote debugging protocol."
msgstr ""
#: howto/remote_debugging.rst:669
msgid "When to use ``PYTHON_DISABLE_REMOTE_DEBUG``"
msgstr ""
#: howto/remote_debugging.rst:671
msgid ""
"The environment variable :envvar:`PYTHON_DISABLE_REMOTE_DEBUG` (and the "
"equivalent :option:`-X disable_remote_debug` flag) allows operators to "
"disable the in-process side of the protocol as a **defence-in-depth** "
"measure. This may be useful in hardened or sandboxed deployment "
"environments where no debugging or profiling of the process is expected and "
"reducing attack surface is a priority, even though the OS-level privilege "
"checks already prevent unprivileged access."
msgstr ""
#: howto/remote_debugging.rst:679
msgid ""
"Setting this variable does **not** affect other OS-level debugging "
"interfaces (``ptrace``, ``/proc``, ``task_for_pid``, etc.), which remain "
"available according to their own permission models."
msgstr ""