Subprocess debugging not working when --pid and --configure-subProcess are used
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Reproduce the issue with python -m debugpy --listen 0.0.0.0:5678 --pid 1 --configure-subProcess True against an application that spawns subprocesses, then attach from VS Code. Compare this with configuring debugpy through debugpy.listen(5678) and verify that subprocesses appear in the Call Stack and accept breakpoints.
Written by the indexing model from the issue text.
Description
Before creating a new issue, please check the FAQ to see if your question is answered there.
Environment data
- debugpy version: 1.8.1 (run
import debugpy; print(debugpy.__version__)if uncertain) - OS and version: Debian GNU/Linux 11 (bullseye)
- Python version (& distribution if applicable, e.g. Anaconda): Python 3.8.18
- Using VS Code or Visual Studio: VS Code
Actual behavior
Debugging session does not recognize subprocesses when debugpy is started using command python -m debugpy --listen 0.0.0.0:5678 --pid 1 --configure-subProcess True
Code running on MainThread works, the issues is with subprocesses.
Debugging sessions work just fine when configuring debugpy from code using debugpy.listen(5678)
Expected behavior
Debugging subprocesses works when launching debugpy using --pid 1 --configure-subProcess True arguments
Steps to reproduce:
- Have an app that spawns subprocesses
- Inject debugpy using command
python -m debugpy --listen 0.0.0.0:5678 --pid 1 --configure-subProcess True - Attach debug session
- Observe subprocesses are not available in Call Stack window and breakpoints don't work.
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 202
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/debugpy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in microsoft/debugpy
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
xinnan-tech/xiaozhi-fde-talk#263 ·
-
rules
Difficulty 1/5 Under an hour Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
huggingface/Repo2RLEnv#163 · 1 comment ·
-
Difficulty 1/5 Under an hour Newbie friendliness 95/100
huggingface/sentence-transformers#4074 ·
-
comp/dashboard invalid P3
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
NousResearch/hermes-agent#121143 ·