-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Remote debug cursor missing in VSCode #899
Comments
Looks like the debugger has stopped at some location that doesn't have a corresponding source.
|
Remote side ls -al /home/djmanas/python:
Local side ls -al /Users/djmanas/Dropbox/Projekty/Python/BSDAdmin.git:
Script to be run BSDAdmin.py you can see on both sides the file is present, the size difference is the comment in front of ptvsd commands:
Launch.json:
MacOS pip3 list:
FreeBSD pip3 list:
It looks like it attaches, even though when I click on the unknown module I see variables that should be there filled in, but wondering what happens, that it is not correctly read by VSC? I am connecting through SSH to the server with -L 4000:127.0.0.1:4000 parameter and it connects. SSH connection is established, nc suceeds. nc -z 127.0.0.1 4000
|
I'm assuming you have opened the folder "localRoot": "${workspaceFolder}", Please try that. |
Nope, still the same.
|
Just to make sure. You mean last stable 2018.4.0? |
Yes |
That's very unusual. |
I have always been „special“ :-( |
@DonJayamanne I have the same error. The call stack shows |
According to the other issue #819, I had tested this one with the experimental python debugger. Used: Configuration,${workspace} didn’t work, since I use workspace with more folders and it launched it only localy, dunno if it is another bug or not, but when I switched it with local path it started to work:
Thank you guys. |
It should be fixed, please test the latest development version of the extension. Instructions can be found here https://github.com/Microsoft/vscode-python/blob/master/CONTRIBUTING.md#development-build I'm closing this issue has I believe it has been resolved in the latest development version. |
Environment data
VS Code version: 1.20.1 (1.20.1)
Python Extension version: 2018.1.0
Python Version: 3.6.4 MacOS, 3.6.4 FreeBSD (both ptvsd 3.0.0)
OS and version: MacOS 10.13.3, Remote FreeBSD 11.1
Actual behavior
I can’t see stepper cursor for debugger, where it is on the line
Configuration is correct, but I guess it might have something to do with „Unknown source“ in call stack, but I have correct directories there.
Expected behavior
I guess it should show me hilighted line, on which the debugger is
Steps to reproduce:
Logs
Output from
Python
output panelOutput from
Console window
(Help->Developer Tools menu)The text was updated successfully, but these errors were encountered: