I am trying to use PyDev to debug a program running on a remote server. My setup is Eclipse 3.3.1, PyDev 1.3.13, and PyDev Extensions 1.3.13; both local and remote hosts are Linux. No problem getting remote pydevd to attach to local debugger. However, I cannot figure out how to set breakpoints in the remote code. Fabio suggested to another user that he could "manually fix that by making the needed changes from the paths from your machine to the other one in some places" (http://sourceforge.net/forum/message.php?msg_id=4533884). But I have identical copies of the code at the same path on both local and remote hosts, so not sure what to do here.
Basically, if your paths are 'exactly the same' in both machines, it should work without any changes... (the files you want to add breakpoints have the same absolute paths on both machines). Now, if that's not the case, I'd advise you to wait for the next release (next week), as I've just changed things so that it's easy to do that mapping (currently you'd have to hack it in more places than you should).
Ok, I've just seen (a bit late) that you said you already have the same identical paths... so, it should be working already...
So, try looking at pydevd.py for "elif cmd_id == CMD_SET_BREAK:" and just put some prints there to see if the breakpoint is correctly set in the remote machine... (as I said, I've already improved that code to give more tracing info, checking if the file exists, etc, but in the current release you'll have to see if that's correctly set with prints...)
Per Fabio's suggestion, I added some print statements to pydevd.py below "elif cmd_id == CMD_SET_BREAK:". They show the correct file path and line number for my breakpoints. However, the debugger still does not stop at the breakpoints. If it matters, the code I am trying to debug is multithreaded, and I do see the thread where my breakpoints should be catching.
What else could be the problem? Debugging <i>does</i> work locally, so I doubt there's an issue with my Eclipse/PyDev setup.