Date:	Tue, 03 Jun 2003 21:22:55 +0300
From:	"Eli Zaretskii" <eliz AT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp AT delorie DOT com
Message-Id:	<7458-Tue03Jun2003212254+0300-eliz@elta.co.il>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to:	<Mv_Ca.7410$JA5.128942@news.xtra.co.nz> (spam@spam.com)
Subject:	Re: Remote debugging over a serial cable
References:	<rYECa.5598$JA5 DOT 93711 AT news DOT xtra DOT co DOT nz> <557-Tue03Jun2003071400+0300-eliz AT elta DOT co DOT il> <Mv_Ca.7410$JA5 DOT 128942 AT news DOT xtra DOT co DOT nz>
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> From: "Vincent" <spam AT spam DOT com>
> Newsgroups: comp.os.msdos.djgpp
> Date: Tue, 3 Jun 2003 22:18:54 +1200
> 
> 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.

It won't.  You need the symbols.

> 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.

Current ports of GDB support graphics modes provided that the BIOS
knows about those modes.  The only other difficulty in debugging such
a program is that the graphics scroll as you type and GDB responds.

- Raw text -