Repository navigation
Attach to local process not working through server WSL2, and no log files are generated. #16921
Description
Steps to reproduce:
Attach to running python 'local process' running on WSL2, should bring up a 'list of processes'
Not sure if this is a supported use case, or if it's a WSL2/VScode issue. But have tested, attaching to 'local process' on SSH connections to other non-WSL targets, and works well. Specifying the process ID manually, on WSL connections also works. This makes me assume there is an issue on ${command:pickProcess} for WSL2 connections?
On WSL2, running the configuration, there is no process selection menu or log file created.
Would be great if someone can confirm.
Environment data
- debugpy version: XXX (run
import debugpy; print(debugpy.__version__)if uncertain) - OS and version: Windows 10, with WSL2 2004
- Python version 3.8
- Using VS Code
Activity
int19h commentedon Jun 16, 2020
If manually specified "processId" is working fine, it's definitely something about the picker.
To clarify, are you using the "Remote - WSL" VSCode feature here?
kissgyorgy commentedon Aug 29, 2020
I have the same problem too. Starting the debug task does bring up the debugger button toolbar, but nothing happens after that. Yes I'm using the Remote - WSL extension, trying to start the debugger in a WSL-enabled project.
SH-BravoAlpha commentedon Dec 21, 2020
Same problem here. This functionality used to work for us with PTVSD but no longer, so switching over to DEBUGPY. Using WSL-Remote Extension with VSCode use a task to launch DEBUGPY server job. Then Remote Attach to the port. The debug task bar loads but there are no entries in Call Stack. Multiple breakpoints set and reflected in log files but no breakpoint is ever hit in VSCODE. Have also tried connecting to PID with no success.
Environment data
debugpy version: 1.2
OS and version: Windows 10, with WSL2 w/Ubuntu 18.04
Python version 3.6.9 64-bit
Using VS Code 1.52.1
- ms-python.python-2020.12.424452561
- ms-python.vscode-pylance-2020.12.2
ruffsl commentedon May 2, 2021
Is this an issue with just debugpy, or a more general issue in vscode that effects other debuggers when using WSL2?
For example, should this issue be escalated to https://github.com/microsoft/vscode-remote-release ?
I just also encountered this issue when attempting to attach a debugging session to a python process running in WSL2.
int19h commentedon Aug 10, 2021
This is a bug in the process picker in vscode-python. This seems to be a common problem with all pickers that are derived from the original Node.js one. Presumably, the fix should also be similar:
microsoft/vscode#75932 (comment)
Note that for Python, the "screen size is bogus" error message doesn't show in the message box. However, if you open Developer Tools and then activate the picker, you'll see it in the console log.
Fix debugger attach to process when running on WSL (#20741)
Merged PR posit-dev/positron-python#58: Merge latest upstream
Merged PR posit-dev/positron-python#58: Merge latest upstream