Beginners problem: Python debugging on remote machine

[RobMeades]

Hi there. I downloaded VisualGDB a few days ago with the aim of editing Python plus C/C++ code for the Raspberry Pi but on a nice Win10 speedy machine/interface and then building/running that code on the Pi. This works with a pure C++ project but I can’t make it work with Python or Python/C++ projects; seems like I have some configuration deeply wrong (not that I’ve consciously touched any configuration) or I have completely misunderstood how VisualGDB is meant to work. In all scenarios I am editing code on a Win10 PC and then building/running the code on the Raspberry Pi (B+) via SSH.

When I create the default Python-only project it appears to “build” successfully (which might not mean anything as there’s no C code to build) but when I attempt to debug it VisualGDB throws an exception before anything starts where it seems to be trying to CD to a Windows directory in a bash script that is presumably running on the Pi:

Your VisualGDB trial expires in 25 days!
 gdb --interpreter mi --args "python" "/tmp/com_sysprogs_PythonDebugWrapper.py" "/tmp/com_sysprogs_PythonBreakpointModule.so" /tmp/VisualGDB/c/Users/Loft/source/repos/PyTest1/PyTest1/PyTest1.py
 bash: line 0: cd: C:\Users\Loft\source\repos\PyTest1\PyTest1: No such file or directory
 -gdb-version

When I create the default Python/C++ project, again the build step is successful but when I attempt to debug it VisualGDB steps into the Python lines as they were compiled from the C source code and so complains at each single step that it cannot find various lumps of glibc source code. Obviously I’m not trying to debug Python itself: is there a way to stop it doing this?

Any help is appreciated.

Rob

[support]

Hi,

Sorry, Python debugging on Raspberry Pi is currently broken. We are investigating this and will post an update here once a hotfix is available (please allow 1-2 working days for that).

[RobMeades]

Got it, thanks for confirming, I’ll try again once fixed.

[support]

Hi,

OK, please try this build: http://sysprogs.com/files/tmp/VisualGDB-5.4.1.2058.msi

Please also follow the instructions in this tutorial to work around the optimization bug in the original Python 3 package.

[RobMeades]

Sorry for the delay, I’ve now purchased VisualGDB to try this out but when I attempt to compile I get:

"Your edition of VisualGDB does not support Linux projects."

I purchased VisualGDB Embedded Edition for GBP84.67 (on 05/03/2018).  Did I miss out Linux somehow?

Rob

[support]

Hi,

Sorry for the confusion. The Embedded edition indeed doesn’t support the Linux-based targets as shown on the feature matrix on the buy page.

If you have purchased the Embedded edition within the last month, you can upgrade it to Linux edition by paying just the price difference here: http://sysprogs.com/splm/mykey (otherwise maintenance period extension surcharge will apply).

 

[meammeiam]

I’m having this same problem with version 5.3R8. Is there a hotfix for this version? Thanks!

• This reply was modified 4 years, 10 months ago by meammeiam.

[support]

Hi,

Version 5.3R8 is very old and indeed may not work with the latest Python versions. Please try updating to VisualGDB 5.5 Preview 7.

[meammeiam]

Does that require purchasing a new license?

[support]

You can find our the latest version compatible with your key, and also manage renewal an upgrade options on the following page: https://sysprogs.com/splm/mykey

[Author]

Posts