Manually Configured Remote Debugging Example

Index of All Documentation » Wing Pro Reference Manual » Advanced Debugging Topics » Manually Configured Remote Debugging »

This example is for manually configured remote debugging only. It is not relevant for users of Wing Pro's Remote Hosts feature.

Here is a simple example that enables debugging a process running on a Linux/Unix host ( using Wing running on a Windows machine ( This example is for wingdbstub users only. If you are using the WingDBG product to debug Zope code, please refer to the Zope Debugging How-To (also included in the WingDBG control panel's Help tab).

On the Windows machine, the following preferences must be specified:

  • Accept Debug Connections should be checked
  • Server Host should be set to All Interfaces (this is the default)
  • Server Port should be set to 50005 (this is the default)
  • Allowed Hosts should be altered by adding

On the Linux/Unix machine, the following value is needed in


Once this is done and Wing has been restarted, you should be able to run code that imports wingdbstub on the Linux/Unix machine and see the debug connection establish on the Windows machine.

Then you will need to set up file sharing between the two machines (for example, using Samba) and will need to establish a location map in your Wing preferences on the Windows machine.

If your source code on the Linux/Unix machine is in /home/myuser/mysource and you map /home/myuser to e: on the Windows machine, then you would enter this location map via the Preferences GUI by adding as a new Remote Host IP and entering a single mapping pair with /home/myuser/mysource and e:/mysource.

See Manually Configured Location Map Examples for additional examples.