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