8000 PEP 768: Safe external debugger interface for CPython by pablogsal · Pull Request #4158 · python/peps · GitHub
[go: up one dir, main page]

Skip to content

PEP 768: Safe external debugger interface for CPython #4158

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 18 commits into from
Dec 9, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
Update pep-0778.rst
Co-authored-by: Jelle Zijlstra <jelle.zijlstra@gmail.com>
  • Loading branch information
pablogsal and JelleZijlstra authored Dec 6, 2024
commit a85ea657d2b8153fbe1a69dc5942d57f4ed3a396
2 changes: 1 addition & 1 deletion peps/pep-0778.rst
Original file line number Diff line number Diff line change
Expand Up @@ -55,7 +55,7 @@ counting system. This combination of low-level system manipulation and
deep domain specific interpreter knowledge makes implementing Python debugging tools
exceptionally difficult.

The few tools ( see for example [1]_ and [2]_ )that do attempt this resort to
The few tools (see for example [1]_ and [2]_) that do attempt this resort to
suboptimal and unsafe methods,
using system debuggers like gdb and lldb to forcefully inject code. This
approach is fundamentally unsafe because the injected code can execute at any
Expand Down
Loading
0