But fear not – you don’t have to write countless ‘prints’ or fiddle with python’s inspect module just to fix a simple fence post error.<\/p>\n
Stepping through breakpoints and browsing your plugins scope… – all this is possible with the PyDev remote debugger.<\/p>\n
<\/p>\n
How does it work?<\/h1>\n
![\"\"](\"http:\/\/www.smart-page.net\/blog\/wp-content\/uploads\/2011\/05\/debug2.jpg\" "\\"debug2\\"")
<\/p>\n
The PyDev remote debugger consists of a server running in Eclipse, listening to a given port – and a client (your plugin), that inspects the scope at runtime and sends it to the server.
\nThis concept has the advantage of working with virtually any host-application one can think of – including Cinema4D.<\/p>\n
The only disadvantages are that you have to add the client module to your source and to insert a small line of code for each breakpoint.<\/p>\n
Setup<\/h1>\n
![\"\"](\"http:\/\/www.smart-page.net\/blog\/wp-content\/uploads\/2011\/05\/debug4.jpg\" "\\"debug4\\"")
<\/p>\n
As the remote debugger comes with PyDev, it’s already installed within your IDE – we just have to find out where exactly as the installation path varies with the PyDev version:<\/p>\n
- \n
- Browse to your Eclipse folder and do a search for a file “pydevd.py”<\/li>\n<\/ul>\n
You should end up with a Path somewhat similar to this:
\n‘C:\\Program Files\\eclipse\\plugins\\org.python.pydev.debug_2.0.0.2011040403\\pysrc’<\/em><\/p>\nIf you find more than one ‘pydevd.py’, make sure you selected the PyDev folder with the latest version number within ‘plugins’.<\/p>\n
- \n
- Now open the source file you wish to debug and insert:\n
import sys\r\nsys.path.append('C:\\Program Files\\eclipse\\plugins\\org.python.pydev.debug_2.0.0.2011040403\\pysrc')\r\nimport pydevd<\/pre>\n<\/li>\n<\/ul>\nAnd that’s it!<\/p>\n
Debugging<\/h1>\n
![\"\"](\"http:\/\/www.smart-page.net\/blog\/wp-content\/uploads\/2011\/05\/debug3.jpg\" "\\"debug3\\"")
<\/p>\nLet’s do a quick test run and place a breakpoint.<\/p>\n
- \n
- Add the line pydevd.settrace() somewhere within your source<\/li>\n
- Switch Eclipse to “Debug View” (upper right) or click ‘Window’ -> ‘Open Perspective’ -> ‘Other’ -> ‘Debug’<\/li>\n
- Start the PyDev remote debug server by clicking the Icon on the top left (the small green bug with the blue ‘P’)<\/li>\n
- Fire up Cinema 4D and switch back to Eclipse<\/li>\n<\/ul>\n
You can now continue or step to other breakpoints by using the small icon bar on the top left or the F5-8 shortcuts.<\/p>\n
The variable tab on the right allows you to inspect your plugins scope in detail.<\/p>\n
In case this doesn’t work, check your firewall settings first before repeating these steps or taking a look at the PyDev documentation<\/a>.
\n
\nTip: <\/span><\/strong>
\nRoute the standard- and error output-channels to the PyDev console with…<\/p>\npydevd.settrace(True, True)\r\n<\/pre>\n
\nWith the debugging feature added, our Python plugin coding environment should now be complete…<\/p>\n
Time to spring into action! \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
When hunting down glitches, the debugger is the coder’s weapon of choice… In the last post about coding advanced Python plugins, this vital part was skipped as Cinema 4D’s Python interpreter doesn’t support it. But fear not – you don’t have to write countless ‘prints’ or fiddle with python’s inspect module just to fix a simple fence post error. Stepping through breakpoints and browsing your … Continue reading Debugging Cinema 4D Python Plugins with PyDev<\/span>
- Now open the source file you wish to debug and insert:\n