#21 browse source files remotely

[Anonymous]

It would be great if winpdb could visit source files and browse source directories across a remote connection. This would be very useful for debugging server side applications where there is no way to open an X connection from the machine where the application is running. Basically there could be some kind of internal proxy in the debugger for os.listdir etc. that would work across the remote protocol. Also the label "open source" in the file menu, in some contexts sounds as if it could refer to software licenses rather than to a debugging action. --Paul R.

[Nir]

Logged In: YES
user_id=933518
Originator: NO

Thanks for the "open source" comment and the usability feedback.
When you open a source file it is always fetched from the environment of the debugged script.
It you are debugging remotely the source will be fetched from the remote machine.
However, browsing is only enabled if you are debugging locally.

I will fix the dialog name and description to reflect this better.

[Nobody/Anonymous]

Logged In: NO

Thanks. It would be VERY helpful to be able to browse remotely. The issue is that I want to set a breakpoint at a particular line in one of the remote files, but there is no way to do that except by browsing the file. Or rather, I can set a breakpoint in the console window (b foo.py:234 or whatever) but hitting the breakpoint doesn't cause the file to get loaded into the debugging window.

[Nir]

Logged In: YES
user_id=933518
Originator: NO

What version of Winpdb are you using?

in winpdb 1.3.2 you should be able to "open source" a remote file and see it in the debug window.
Also if a breakpoint is hit the file should load in the debug window.

Note that setting a breakpoint and a breakpoint being hit are two different things.

If this does not happen on your system please post more details on this problem.

[Nobody/Anonymous]

Logged In: NO

Aha, I'm using 1.3.0 and didn't realize anything like this had changed. I'll install 1.3.2 and see what happens. Thanks. --Paul

[Nobody/Anonymous]

Logged In: NO

OK, I'm now using 1.3.2 at both the local and remote ends, and the file menu is completely greyed out except for "exit". The remote side is under a rather messy linux setup which I can't easily change, unfortunately. But I can try running the program on another machine with a more straightforward setup. The local side is a more straightforward kubuntu installation.

[Nobody/Anonymous]

Logged In: NO

If I set the breakpoint manually with the bp command, the code now comes up in the source window, which lets me debug without needing to open the file from the file menu. It would be great if the file menu worked, but it's just a convenience issue now, and the main problem is solved. Thanks for the help!