remote gdb with shared serial port

[Luke Diamand]

"Robert J. Brown" wrote:
> 
> I am working on project now with an embedded 68332.  For legacy
> reasons, they are stuck with the MRI compiler.  I want to use
> cross/remote gdb as a debug tool.  This is mostly old code that
> sufferes from being hacked a lot -- it is a test fixture, not a
> shipped product -- so I want a good debugger to help me navigate thru
> the spaghetti.  :-)
> 
> First question:  What format are the object files produced by the MRI
> 68K compiler for this target?
> 
> Second question:  There is only one serial port on this box, and it is
> used to communicate between the workstation and the box during normal
> operation.  I will need to share this serial port for gdb to work.
> The box is plugged into the serial port of an NCD X-terminal, so the
> host computer must communicate with the serial port via a socket, such
> as a telnet connection.  Can I use an escape character, such as ^C to
> get the xgdb driver's attention in the target box, and likewise to
> switch the socket between the host copy of gdb and the host software
> that normally talks to the box?

We use bit 8 - stuff with bit 8 set goes to the debug stub/gdb, while
stuff without bit 8 set is seen by humans. Of course it only works if
you are using English, or one of its variants :-).

> 
> Third question:  Where is the latest version of gdb located?  I tried
> to ftp from prep.ai.mit.edu, but it kept timing out.  :-(
ftp://ftp.funet.fi/pub/gnu ?

HTH!
Luke Diamand

-- 
Virata http://www.virata.com
Cambridge
Tel: +44 1223 566919      Fax: +44 1223 566915

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sourceware.cygnus.com