Debug cant set breakpoint on project on windows drive mapped by sshfs
I have a project on D: drive. it is a network drive mapped via sshfs to a remote linux folder, created by:
net use d: \\sshfs.r\me@mylinuxremote.com /persistent:yes
This works fine for editing, searching and everything else. But when adding a breakpoint I get an error like this:
pydev debugger: warning: trying to add breakpoint to file that does not exist: \\sshfs.r\me@mylinuxremote.com\path\to\myproject\pkg\mymodule.py (will have no effect)
Is there a way to fix this? I know that the pro version has some special support for remote project but I am looking for answer if I can do it this way with CE. why cant debugger access the file the same as the rest of pycharm, ie by the mapped path d:\path\to\myproject\pkg/mymodule.py?
To save a question, the interpreter happens to be a local virtualenv on the localbox, but I do not think that is relevant to how pydev is trying to open the file.
Please sign in to leave a comment.
ps at some point I tried SFTPDrive which only supports one drive mapped at a time in the free version. I had gotten debugging to work with SFTPDrive, but trying it again now, I get a similar error: pydev debugger: warning: trying to add breakpoint to file that does not exist: \\mylinuxremote.com\mydrivename\path\to\pkg\mymodule.py (will have no effect)
Hi,
What path to the file is shown when you however over the tab? Does it refer to normal or UNC path?
when I hover on the editor tab, it shows the normal path eg d:\path\to\pkg\mymodule.py
Yes, this is strange. Generally it's not recommended to work on a project files located on network drives due to performance issues with indexing, but it shouldn't affect the debugger.
Could you please submit a bug report to https://youtrack.jetbrains.com/issues/py with the steps to reproduce the issue and some screenshots to demonstrate? Also, please attach Logs from **Help | Collect Logs and Diagnostic Data** after reproducing the issue.
I just noticed, the error says ...does not exist: \\sshfs.r\me@myserver\path\to\pkg\module.py, but in fact the file on the server is \path\To\pkg\module.py
so out of curiousity, i did ln -s /path/To /path/to on myserver
Then it worked! so somewhere along the line, the filename is getting lower-cased.