From: "Vincent" Newsgroups: comp.os.msdos.djgpp References: <557-Tue03Jun2003071400+0300-eliz AT elta DOT co DOT il> Subject: Re: Remote debugging over a serial cable Lines: 58 X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Message-ID: Date: Tue, 3 Jun 2003 22:18:54 +1200 NNTP-Posting-Host: 210.86.20.50 X-Complaints-To: newsadmin AT xtra DOT co DOT nz X-Trace: news.xtra.co.nz 1054635116 210.86.20.50 (Tue, 03 Jun 2003 22:11:56 NZST) NNTP-Posting-Date: Tue, 03 Jun 2003 22:11:56 NZST Organization: Xtra To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Eli, thanks for your response. I'll try to search the archives of the newsgroup for any mention of remote debugging. FYI: The program I'm trying to debug runs on the DOS platform (Imagine a plain DOS machine - no Windows - and that's pretty much what I'm playing with here). I compile on WinXP using DJGPP, and pretty much copy it over (via floppy) to the target machine. I also use UPX to compress the executable (original size is about 11MB, compressed to about 700kb). I think UPX strips symbols from the exe. Given that I use UPX, I'm not sure whether remote debugging (or even using GDB) would work. Even if it did, the symbol file would probably be too big to copy onto a floppy to transfer to the target machine. The application also uses the CWSDPMI stub - but I think GDB should handle this. And supposing I did have GDB, the .exe and symbols on the target machine, the application uses graphics - so command-line operation will be difficult. Any ideas welcome. Current debugging methods are logging to a file - and then figuring out what happened; which is hardly an attractive thing to do. ps. It's a long story why I'm compiling for DOS, let alone using an DOS machine...just don't ask :-) "Eli Zaretskii" wrote in message news:557-Tue03Jun2003071400+0300-eliz AT elta DOT co DOT il... > > From: "Vincent" > > Newsgroups: comp.os.msdos.djgpp > > > > Is it possible to remote debug a program compiled with DJGPP over the serial > > port, where the target is DOS, and the host is Win2k or XP. > > > > I've seen the documentation for gdb and gdbserver; and there's no mention of > > gdbserver running in DOS. > > Remote debugging of DJGPP programs is possible, but not all of the > necessary code is part of the official GDB distribution. > > I suggest to search the archives of this news group for relevant key > words; I think someone who did succeed in making remote DJGPP > debugging happen posted information about that here. > > That said, could you please tell why can't you use the ordinary > debugging procedure with the gdb.exe executable? It does run on > Windows, AFAIK.