Anyone using a cross-debugger?

Jeremy Peterson wrote:

Has anyone had any luck using a cross-debugger to debug SDL application
cross-compiled for Win32. The man for gdb mentions the possibility to
use a serial link or possibly even a TCP/IP socket to communicate to a
stub gdb running on the Win32 machine hosting the cross-compiled app.
But I haven’t been able to find this stub anywhere ( cygnwin, gdb
sources, … ).

Whaddya know, this is something I know about! It’s marginally offtopic,
so I’ll keep it short. The theory is that there is a simple ASCII
protocol that goes over the line, with the full GDB + sources sitting
on a host (which could be any kind of system, Linux for instance), and
on the target Win32 machine you have a “stub” that interprets the
protocol packets and does the actual controlling of the program being
debugged. Sort of a “debugging proxy”, actually.

Alas, the practice is that no one has written a stub specifically for
Win32. It would not be hard though, all the pieces are in GDB sources
already. Look at gdb/win32-nat.c to see how to control a Win32 app,
gdb/gdbserver to see how stubs are put together for cross-Unix debugging,
gdb/wince-stub.[ch] for Windows CE, gdb/i386-stub.c for generic x86
stub. The most obvious thing to do would be to add a gdbserver/low-win32.c
cribbed from win32-nat.c, and beat the code into submission. If you do
decide to pursue this, the GDB folks (which includes me) will be very
glad to get the code; if you have more questions about how to make it
work, mail to gdb at sourceware.cygnus.com.

Stan

Has anyone had any luck using a cross-debugger to debug SDL application
cross-compiled for Win32. The man for gdb mentions the possibility to
use a serial link or possibly even a TCP/IP socket to communicate to a
stub gdb running on the Win32 machine hosting the cross-compiled app.
But I haven’t been able to find this stub anywhere ( cygnwin, gdb
sources, … ).