confusion about installing remote debugger

[mike rodent]

Hi,
Using Jython (2.5) in PyDev (2.0.0) in Eclipse Helios (3.6.1).

Debugging simply does not work on multiple threads… searching seemed to indicate that the thing to do was to install the PyDev remote debugger: manual: http://pydev.org/manual_adv_remote_debugger.html  <- but these buttons are not present in my toolbar at all (!) and I can find now menu equivalent to launch the remote debugger.

Also found this page from here: https://sourceforge.net/projects/pydev/forums/forum/293649/topic/3549899
Tried experimenting with this but it appears that this is sthg you do *after* getting the remote debugger up and running.

Anyone know how I install the remote debugger?

Thanks

[Fabio Zadrozny]

Those buttons should be present at the debug perspective.

You can enable them in other perspectives in window > customize perspective > command groups availability > pydev debug.

Aside from that, I think that http://pydev.org/manual_adv_remote_debugger.html should explain properly how to use it (just a note: the debugger should work with threads created in Jython, but sometimes, if they're created in Java, PyDev doesn't know about it and thus doesn't add debugging to that thread - and the same happens on some swing calls).

Cheers,

Fabio

[mike rodent]

Thanks… in fact CommandGroups -> PyDev Debug was unticked both for normal and debug perspective.

So I ticked em… Followed through the manual-adv-remote-debugger instructions… unfortunately it didn't work because, yes, I am essentially using threads created in Java… SwingWorker's non-EDT thread in doInBackground(), and EDT in process().  Breakpoints non-functional.

Do you have any knowledge on how big a challenge the PyDev developers would face to do sthg about this?  If reasonable, is it anywhere on their radar  to your knowledge?

[Fabio Zadrozny]

Actually, if you use the remote debugger, when you call 'import pydevd;pydevd.settrace()', it should properly treat that line as a breakpoint and stop over it… doesn't that happen for you?

[mike rodent]

no, it doesn't stop at that line unless I explicitly put a breakpoint on it.

I get the message "pydev debugger: starting" in the console panel … but it doesn't stop there.  Strange because I followed all the instructions and believe the remote debugger is indeed running… Is it possible that it isn't working properly and that it is just doing a normal non-remote debug?