Yeah it is pointing to the same installation (the only one). However import pydevd from the console does not work (no module pydevd). But the same setup is with the other (newer) installation - i cannot import pydevd through the console, but the remote debug configuration points to the right pydevd folder and breakpoints work.
d. ginetto wrote > did you check if you are pointing the same pydevd installation from > qgis to aptana/pydev installation? > > check in the qgis python console the path used to load the pydevd module > > e.g. > >>>> import pydevd >>>> pydevd > <module 'pydevd' from > '/mnt/data/PROGRAMMING/IDE/eclipse-cpp-mars-2-linux-gtk-x86_64/plugins/org.python.pydev_4.6.0.201605031722/pysrc/pydevd.pyc'> > > Luigi Pirelli > > ************************************************************************************************** > * Boundless QGIS Support/Development: lpirelli AT boundlessgeo DOT com > * LinkedIn: https://www.linkedin.com/in/luigipirelli > * Stackexchange: http://gis.stackexchange.com/users/19667/luigi-pirelli > * GitHub: https://github.com/luipir > * Mastering QGIS 2nd Edition: > * > https://www.packtpub.com/big-data-and-business-intelligence/mastering-qgis-second-edition > ************************************************************************************************** > > > On 30 December 2016 at 19:21, krwoloq < > dalibor.kusic@ > > wrote: >> Hi! >> >> I have two installations of QGIS - one 2.6.1 for my legacy project and >> the >> newer 2.16.1. I'm trying to use the remote debugger on the 2.6.1. >> >> On both installations I did the same thing: >> * Install Eclipse with PyDev (Aptana Studio) >> * Install Remote Debug plugin >> * Configure remote debug plugin with the pydevd path from Aptana >> installation >> * Create a linked folder in Aptana to the plugin source file >> * Put a breakpoint in the .py source >> * Start PyDev Debug Server (shows Debug Server root and Debug Server >> node) >> * Start remote debug in QGIS (shows "unknown" node under Debug Server >> root) >> * Run the plugin >> >> But, in my 2.6.1 installations breakpoints do not work (in 2.16.1 it >> works >> fine). What could I be missing? I can still suspend the code "manually" >> by >> using settrace or suspending the thread in PyDev (it breaks on the first >> next call), however I can't get the breakpoints to work :( Any idea? I >> don't >> think I did anything different on the 2.16.1 installation that does work. >> >> d. >> >> >> >> -- >> View this message in context: >> http://osgeo-org.1560.x6.nabble.com/PyDev-debug-breakpoints-tp5301651.html >> Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. >> _______________________________________________ >> Qgis-developer mailing list >> > Qgis-developer@.osgeo >> List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer >> Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer > _______________________________________________ > Qgis-developer mailing list > Qgis-developer@.osgeo > List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer -- View this message in context: http://osgeo-org.1560.x6.nabble.com/PyDev-debug-breakpoints-tp5301651p5301778.html Sent from the Quantum GIS - Developer mailing list archive at Nabble.com. _______________________________________________ Qgis-developer mailing list Qgis-developer@lists.osgeo.org List info: http://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: http://lists.osgeo.org/mailman/listinfo/qgis-developer
