pydev debugger: warning: trying to add breakpoint to file that does not exist
Answered
I use a mac and this error->
pydev debugger: warning: trying to add breakpoint to file that does not exist:
keeps upcoming, I have to work with a remote VM but my path always directs to the local project path and not the VM. I have tried setting up my interpreter and changed my paths but still, this error pops up.
please let me know if there is a solution for this.
Please sign in to leave a comment.
I'm seeing this as well with WSL2, attempting to set a breakpoint in an installed library package. This work around does not work - I do not see the entry in my registry.
I am also getting the same warning while using Pycharm debugger. How can I solve this?
pydev debugger: warning: trying to add breakpoint to file that does not exist:
same problem after update. It was last time when I updating pycharm :-( every time worse and worse
I am also experiencing this in an environment managed by vagrant. When I start the debugger I get a long list of warnings (perhaps I'll remember to cleanup some of my breakpoints)
When I ssh to the vagrant machine and look in the temp directory it is very much empty and I'm at a loss as to where the files actually are other than my /vagrant mountpoint where my source root is mapped.
Hello,
>I have to work with a remote VM but my path always directs to the local project path and not the VM.
Could you please provide it with more details here? Do you use SSH interpreter?
>changed my paths but still,
Please attach a screenshot of the current state and
Run/Debug Configuration https://www.jetbrains.com/help/pycharm/creating-and-editing-run-debug-configurations.html
Hi yes, I use SSH interpreter,
Do you have this file locally and on the remote host?
Is the local directory the file is in mapped to a correct directory on the remote host in File | Settings | Build, Execution, Deployment | Deployment?
Your SSH interpreter should have the same project mapping.
yes, the path is correctly given. even the interpreter is mapped to one in the host.
Could you file a ticket to https://youtrack.jetbrains.com/issues/PY and attach screenshots showing your deployment configuration and SSH interpreter?
It will be easier to troubleshoot it in YouTrack.
I'm very sorry for the inconvenience.
Most likely you are experiencing this issue https://youtrack.jetbrains.com/issue/PY-55821/No-mapping-of-remote-sources-from-SSH-interpreter
We are working on the fix.
also having almost same problem.
I usually work on windows10 host machine to ubuntu remote server.
It worked fine, however, recently I changed my host machine to MacBook Air, and having this issue.
I have tried removing previously using settings of remote interpreter, ssh deployment, and mappings.
and it works for the firsttime, however, I rerun the debug mode, it shows the message
Not sure what cause this issue, but i doesn''t happen on Windows10 client machine.
I hope this get fixed somehow. no clue after suffering 2 weeks of hacking.
Pcbank1 could you please report it to https://youtrack.jetbrains.com/issues/PY?
Provide screenshots showing your deployment path mappings and the whole console output from the debugger.
We'll investigate it.
I have the same issue via WSL. It complains about the scratch file not existing. The scratch file runs fine.
I'm having the same issue as Shaun Kruger above, in a Vagrant virtual machine. The /tmp folder is also empty. I tried destroying the vagrant machine and creating it again and the problem persists (I guess it may be some metadata in the .idea folder?). How could I try to figure out what's going wrong? There are no deployment mappings in this case.
Hi @..., We had a similar issue reported where recreating the .idea folder helped. Check out the following comment: https://youtrack.jetbrains.com/issue/PY-55285/trying-to-add-breakpoint-to-file-that-does-not-exist-after-updating-to-2022.2#focus=Comments-27-7822843.0-0
In case the issue persists, please create a new report directly at https://youtrack.jetbrains.com/issues/PY so you can share additional logs and details.
Hi Montiero, I don't see a comment in this issue. https://youtrack.jetbrains.com/issue/PY-55285/trying-to-add-breakpoint-to-file-that-does-not-exist-after-updating-to-2022.2#focus=Comments-27-7822843.0-0
I'm having this problem in 2023.2.4, Build #PY-232.10203.26, built on November 1, 2023.
Hi Jim Katz , please update to recent 2023.3.1 . Can it be resolved this way?
That had no effect.
```
/usr/local/bin/python /home/jimk/.pycharm_helpers/pydev/pydevd.py --multiprocess --qt-support=auto --client localhost --port 42367 --file /home/jimk/dev-remote/archive-ops/scripts/processing/get-correlated-files.py --arc-root /mnt/Archive -vv --list home/jimk/prod/specialMonlam/src/W19834/images/W19834-I1GS105561/I1GS1055610003.jpg
Connected to pydev debugger (build 233.11799.298)
pydev debugger: warning: trying to add breakpoint to file that does not exist: /tmp/r4wq5o94XX/scripts/processing/get-correlated-files.py (will have no effect)
```
Jim Katz , please create a new report directly at https://youtrack.jetbrains.com/issues/PY attaching logs from Help | Collect Logs and Diagnostic Data