![]() |
Winpdb Remote Debugger ported to RobotPy
Hey, I've been playing with RobotPy quite a bit lately, and one thing you'll probably note is that debugging scripts is a bit annoying. Ok, more than just a bit annoying... haha. Anyways, here's a great solution to solve that problem! Winpdb is a GPL remote debugger that works pretty well from what I can see so far, and gives you full source debugging over the network. I've modified it a bit so that it works on RobotPy. Check it out:
http://www.virtualroadside.com/blog/...py-on-vxworks/ Note: Contrary to its name, Winpdb is cross platform, it just requires wxPython to run. |
Re: Winpdb Remote Debugger ported to RobotPy
Sounds like this will really help! Unfortunately, I can't try it out on our robot until Monday. D:
|
Re: Winpdb Remote Debugger ported to RobotPy
Speaking of debugging, have you found a way to compile and check your scripts *before* running on the robot?
In Java NetBeans would compile our code locally and show where we had syntax errors or improper API calls, but with Python we don't find this out until runtime. This makes it hard to work on code when there is no robot access, since someone's usually working on it mechanically. So far I can check syntax with: python3.1 -c "import py_compile; py_compile.compile('robot.py')" However that does not seem to catch many of the problems we'll run into, like misspelling function names and other common errors. Any ideas? |
Re: Winpdb Remote Debugger ported to RobotPy
Quote:
|
Re: Winpdb Remote Debugger ported to RobotPy
i have a virtual robot thing half put together
Code:
#This file should emulate enough of wpilib to make it usable for testingWow, i was high when i wrote this, pasted wrong file |
| All times are GMT -5. The time now is 19:52. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi