public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
* Remote Debugger
@ 2001-04-20  6:20 deepak shekhar
  2001-04-26 14:42 ` J.T. Conklin
  0 siblings, 1 reply; 3+ messages in thread
From: deepak shekhar @ 2001-04-20  6:20 UTC (permalink / raw)
  To: gdb

Hi everybody ,

I am porting GDB for an hypothetical processor.
It is a remote debugger that is., the processor is  connected to the host machine via serial port.
As a part of it i am writing the following files remote-hypo.c and hypo-tdep.c &tm-hypo.h.

Can somebody explain me how actually the GDB executes the program on the target processor??
Which  available port is a good example to follow??

Any help is appreciated.
thanks in advance
Deepak


_____________________________________________________
Chat with your friends as soon as they come online. Get Rediff Bol at
http://bol.rediff.com




^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Remote Debugger
  2001-04-20  6:20 Remote Debugger deepak shekhar
@ 2001-04-26 14:42 ` J.T. Conklin
  0 siblings, 0 replies; 3+ messages in thread
From: J.T. Conklin @ 2001-04-26 14:42 UTC (permalink / raw)
  To: deepak shekhar; +Cc: gdb

>>>>> "deepak" == deepak shekhar <dipaktc@rediffmail.com> writes:
deepak> I am porting GDB for an hypothetical processor.  It is a
deepak> remote debugger that is., the processor is connected to the
deepak> host machine via serial port.  As a part of it i am writing
deepak> the following files remote-hypo.c and hypo-tdep.c &tm-hypo.h.

Unless there is some specific requirement that you have not stated,
there is no need to have a target specific mechanism for gdb/target
communications (ie. remote-hypo.c).  The target independent generic
remote serial protocol should be sufficient.

deepak> Can somebody explain me how actually the GDB executes the
deepak> program on the target processor??

Many people use GDB to download the program to the target.  For many
targets GDB uses a special download mechanism (streaming s-records,
using a bulk transfer protocol like xmodem or tftp, etc.), but most
simply do multiple writes.  The targets I'm responsble for load the
image via tftp or off flash, so GDB is not involved in downloading.

Once the program has been downloaded, GDB sets the program counter to
the first instruction, and when instructed sends a continue or step
command.  That's it.  The program is running.  GDB then waits for
notification that the program has stopped.

deepak> Which  available port is a good example to follow??

My advice is to go with a target that is most like your hypo cpu.  But
take advantage of all the other targets as examples.  Also be sure to
read the GDB internals manual.

        --jtc

-- 
J.T. Conklin
RedBack Networks

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Remote Debugger
@ 2001-04-20  6:22 deepak shekhar
  0 siblings, 0 replies; 3+ messages in thread
From: deepak shekhar @ 2001-04-20  6:22 UTC (permalink / raw)
  To: gdb

Hi everybody ,

I am porting GDB for an hypothetical processor.
It is a remote debugger that is., the processor is  connected to the host machine via serial port.
As a part of it i am writing the following files remote-hypo.c and hypo-tdep.c &tm-hypo.h.

Can somebody explain me how actually the GDB executes the program on the target processor??
Which  available port is a good example to follow??

Is any documentation available other than the the one that come with the sources???? Please indicate if any..

Any help is appreciated.
thanks in advance
Deepak


_____________________________________________________
Chat with your friends as soon as they come online. Get Rediff Bol at
http://bol.rediff.com




^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2001-04-26 14:42 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-04-20  6:20 Remote Debugger deepak shekhar
2001-04-26 14:42 ` J.T. Conklin
2001-04-20  6:22 deepak shekhar

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).