|
From: Christopher F. <cg...@re...> - 2003-07-20 22:27:32
|
On Wed, Jul 16, 2003 at 01:33:39PM +0300, Kai Ruottu wrote: >"Kai Ruottu" <kai...@lu...> wrote: > >> BTW, the WinCE-target support in GDB includes stuff like 'gdb/wince.c' and >> 'gdb/wince-stub.c' which also use the Windows-sockets (winsock) ? for some >> purpose: > >If one looks at the 'wince.c', the part running on Win32, and >'wince-stub.c', the part running on WinCE, one easily gets the thought >that the same maybe could be implemented for the Win32-to-Win32 remote >debugging. So a WinNT/2k/XP system which should be much more stable as >the development platform, could be used as the debug host for debugging >Win32 stuff running on Win95/98/ME, which is the equivalent of the >WinCE, "a stripped model of the real Windows". I wrote wince.c and wince-stub.c, although these days, I try to disavow all association with that code. I did try to write it in such a way as to make it extensible but I don't think these two files should be used for remote debugging and can say with some confidence that a solution employing that technique would probably not be accepted in gdb. Corinna Vinschen wrote a stub for the 'rda' program which serves the same purpose as what I did and uses standard gdb remote protocol mechanisms rather than the hacks that I used. There isn't a rda web page detailing how to get the sources but there is a mailing list "rd...@so..." where you can ask about how to get the sources. I'm pretty sure that if someone wanted to spend time fixing up rda to do what was required for remote debugging, it would be accepted. And, it should even work with a standard gdb. cgf |